Wider progress bar in Dogecoin Core

Describe the issue
Poor space management, lots of empty space. Especially when the entire bar is over 7 years, it's hard to read or see any progress on the bar when it's so narrow, you're pretty much forced to look at the blocks change or other information.
Expected behaviour
Fill up the empty space, make use of it.
Screenshots.

What version of Dogecoin Core are you using?
1.4.3

This is the norm for every blockchains QT client.   Also, this progress bar really means nothing.  Sync times depend on several things including:
Your Internet connection speed
ability to connect to a peer
power of your computer i.e. ram/cpu specs
.conf settings
etc


Add test script to composer.

Coverage remained the same at 100.0% when pulling 230ea048fbbfac2bff039830ba6f37af8c7fc5a0 on composer-test into 6c6547858f9e73be1aff966511e09287e81f693c on master.


Update to ensure main content area fills display height.

Ensure the app height is filled regardless of screen size
Description

Removed unnecessary div from to main component
Updates to base styling to ensure body is 100% and main area flexes to fill

Related Issue
N/A
Motivation and Context
Better user experience
How Has This Been Tested?
Local Testing
Screenshots (if appropriate):

Looks good.


Update with $set on array fields throw conflict

I have collection Products with schema :
name: {
    type: String,
    index: 1
  },
  slug: { type: String, slug: ["name"], slugPaddingSize: 0, unique: true },
other_image_ids: {
     type: Array,
}

When i update with
Products.updateOne({_id: id}, {$set: { name: "test", other_image_ids: [{name: "imagename"}] }}, { new: true })

Mongo will throw error :
MongoError: Updating the path 'other_image_ids.0.name' would create a conflict at 'other_image_ids'

Package version
mongoose: 5.4.0
mongodb: 3.1.10
mongoose-slug-updater: 3.0.4

Hi @vilipwong,
take a look here
If you want to update document with object as a value - try to remove $set operator.
This operator intended to make point changes by fully qualified string path like this:
{ $set: { name: 'test', 'other_image_ids.0.name': 'imagename' } }

Also note:
this behavior wasn't caused by mongoose-slug-updater,
you can try to remove plugin in your code and you will get the same issue.

I'm using this query before and works fine. I tried removing slug and no error thrown. I'll try to dig around. Thanks.

Please double check there is no error without plugin.
Look:
https://gist.github.com/YuriGor/6aaae88635c629839744dc28f6d36faf
your error reproduced without plugin.

Yes, I reproduced it finally, I'll see what's hapenning.

Just fixed this bug, thank you for reporting!
Please let me know if it works for you now.

@vilipwong dont forget to get latest 3.1.1 version


chore: replace logger framework

With this new logger we can easily log into a file and into the console.
Second commit is optional, let me know if you want to keep it or drop it.
Initial few log files look like this:
flutter: [I] TIME: 2023-10-06T15:41:17.320986 r: Initialized logger
flutter: [I] TIME: 2023-10-06T15:41:17.656526 Coordinator version: 1.3.0
flutter: [I] TIME: 2023-10-06T15:41:17.657005 Client is up to date: 1.3.0
flutter: [I] TIME: 2023-10-06T15:41:19.653350 App data will be stored in: /Users/bonomat/Library/Developer/CoreSimulator/Devices/BBD86D27-7B1E-4237-BBDB-34FF9F250C78/data/Containers/Data/Application/E8A20B9D-0E4D-4568-A60C-5FD5FA6337D4/Documents
flutter: [I] TIME: 2023-10-06T15:41:19.653961 Seed data will be stored in: /Users/bonomat/Library/Developer/CoreSimulator/Devices/BBD86D27-7B1E-4237-BBDB-34FF9F250C78/data/Containers/Data/Application/E8A20B9D-0E4D-4568-A60C-5FD5FA6337D4/Library/Application Support
flutter: [D] TIME: 2023-10-06T15:41:19.661211 r: Parsing config from flutter config: Config { coordinator_pubkey: "02dd6abec97f9a748bf76ad502b004ce05d1b2d1f43a9e76bd7d85e767ffb022c9", esplora_endpoint: "http://<IP_ADDRESS>:3000", host: "<IP_ADDRESS>", p2p_port: 9045, http_port: 8000, network: "regtest", oracle_endpoint: "http://<IP_ADDRESS>:8081", oracle_pubkey: "16f88cf7d21e6c0f46bcbc983a4e3b19726c6c98858cc31c83551a88fde171c0", health_check_interval_secs: 2 }
flutter: [D] TIME: 2023-10-06T15:41:19.685110 r: Database migration run - db initialized

Log file for the app in the simulator will be located in  (depending on your device id)
~/Library/Developer/CoreSimulator/Devices/BBD86D27-7B1E-4237-BBDB-34FF9F250C78/data/Containers/Data/Application/A654B954-9614-40F7-9984-1C253FF929E4/Library/Application Support/app_log.log
@klochowicz : this solves the problem of losing logs for the app as the logs are stored in a file right away.
fixes: https://github.com/get10101/10101/issues/1202

@klochowicz : this solves the problem of losing logs for the app as the logs are stored in a file right away.

Thanks for tackling this, I've reopened #1092 as this was the suggestion in that issue.
one addition though: for this to be useful in development, we should tackle #1202 as well. It's hard to piece this information together otherwise.

one addition though: for this to be useful in development, we should tackle https://github.com/get10101/10101/issues/1202 as well. It's hard to piece this information together otherwise.

You make it sound like this PR would not be useful unless we do https://github.com/get10101/10101/issues/1202 😅
Anyway, I did it :)

Second commit is optional, let me know if you want to keep it or drop it.

I don't care to much for this prefix either way I am ok.


main.go: Add grpc server path check

I keep the config in controller config and add a new CLI argument called grpc_server_file_path.
If the GrpcServerFilePath is both configured in controller config and defined via grpc_server_file_path, grpc_server_file_path will override the configuration in controller config. And if neither GrpcServerFilePath nor grpc_server_file_path is defined, operator will exit will error code 1 and output an error log.
Signed-off-by: Ce Gao<EMAIL_ADDRESS>

I signed it

I signed it!

/ok-to-test

Let me know when this is ready for another look.


Undefined method `match?' for nil:NilClass when processing response without content type

Hello,
I'm currently encountering an issue when there is no content type available in the response of the http request:
Error: undefined method `match?' for nil:NilClass

          pattern.is_a?(Regexp) ? type.match?(pattern) : type == pattern
                                      ^^^^^^^
.../faraday-decode_xml-0.2.0/lib/faraday/decode_xml/middleware.rb:41:in `block in process_response_type?'

The issue is due to the response_type method which returns nil instead of an empty string:
def response_type(env)
  env.response_headers["Content-Type"].to_s.split(";", 2).first
end

Regards

Fixed with 0.2.1 https://rubygems.org/gems/faraday-decode_xml/versions/0.2.1

Thank you for the quick fix!


Delete attachments after reaching client

Could you make it so that any attachments are deleted from the server when they reach the client so that any VM's with low storage space can continue to use it without taking a lot of storage up.

On the server settings page, there is an Attachment Management section where you can see the current size and delete/clear the caches. I've also just pushed code to delete the attachment after sending.


Use Aura to send system notifications

CommunityToolkit.WinUI.UI.Notifications packages should be used for Windows (You can look at WinUI project for Application as thats what implemented for ShellNotificationSent)


library

Describe your suggested feature
need add interval custom update in minute,8 hours seems too long for refresh
Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open issue.
[X] I have written a short but informative title.
[X] If this is an issue with an extension, I should be opening an issue in the extensions repository.
[X] I have updated the app to version 1.8.2.
[X] I will fill out all of the requested information in this form.

No


Miltinodesupport

Added nodename as label. Changed Gauge to gaugeVec. Before more than one node was not handled correctly.

@kbudde thanks for your Pull Request!
It looks good, but we will test it on Monday to be sure if everything works fine with Prometheus :).

@kbudde works like charm. Merged.


fix for Index of type category fails on validation #840

hey @kuutsav I significantly cleaned up the Index schema component code of concern, thanks for kicking this change off!
Would you mind adding a test case in https://github.com/pandera-dev/pandera/blob/master/tests/core/test_schema_components.py to make sure we can prevent regressions on the issue? https://github.com/pandera-dev/pandera/issues/840

hey @kuutsav I significantly cleaned up the Index schema component code of concern, thanks for kicking this change off!
Would you mind adding a test case in https://github.com/pandera-dev/pandera/blob/master/tests/core/test_schema_components.py to make sure we can prevent regressions on the issue? #840

Sure @cosmicBboy, will add some tests before this weekend.

going to merge this now, going to keep #840 open until a PR with tests containing the case described in https://github.com/unionai-oss/pandera/issues/840#issue-1215731593 is merged.
The simplification in Index validation code is welcome tho thanks @kuutsav !


ImVec2 resetting to zero unsafely

What is the current behaviour?
data[^1].padding is ImVec2(x: 0f, y: 0f).

Please provide the steps to reproduce and if possible a minimal demo of the problem

import nimgl/imgui

type Toast = object
  title*: string
  content*: string
  padding*: ImVec2
  opacity*: float32
  separator*: bool

var data: seq[Toast]

data.add(Toast(padding: ImVec2(x: 10, y: 10)))

assert data[^1].padding == ImVec2(x: 0, y: 0)

What is the expected behaviour?
data[^1].padding to be ImVec2(x: 10f, y: 10f),

Please tell us about your environment

Version: 1.3.2
OS: Linux
Bindings: ImGui
Backend: CPP
Nim Version: 1.6.5
Compiler used: GCC

Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, docs.gl, documentation etc)

Toast should be a ref object.
import nimgl/imgui

type Toast = ref object
  title*: string
  content*: string
  padding*: ImVec2
  opacity*: float32
  separator*: bool

var data: seq[Toast]

data.add(Toast(padding: ImVec2(x: 10, y: 10)))


using MS library for command line parsing

Completely rewritten command line class in order to utilize Microsoft's library System.CommandLine (Github repo https://github.com/dotnet/command-line-api). Resolves #22
Major changes:

help switches require -- in front
it is now azmi --help and not just azmi help (tests updated)
subcommands require argument names in front of argument values because the library has no support for positional parameters (not updated in tests!)
it is now azmi gettoken --endpoint storage
argument short names can be used also, i.e. instead of --endpoint, one can use just -e
(new functionality) application is now returning non-zero exit codes (not updated in tests!)
exit code 1 - parser errors
exit code 2 - subcommand invocation error (with short message displayed)

ToDo before merge:

[ ] - resolve conflicts in azmi-commandline.cs
[ ] - integrate getblob into this PR
[x] - update integration test with argument names
[x] - check for failure codes from operations in integration tests

Integration tests will be temporary broken. @MangyCoyote working on new version in #12 . Marking two PR tasks as completed.

one more task done, integrated getblob within commit https://github.com/SRE-PRG/azmitool/pull/21/commits/01c754830ff38ec2102015d9a972251592f713fc


Components are not pure

First, Thanks for the awesome work.
Even tho the components you've written are all stateless components, they are still not treated as pure by React; which means that React will re-render them all even tho their props did not change.
See facebook/react#5677
I understand that Layout components like Container, Box should not behave this way otherwise child components would not be rendered at all. but leaf components such as Button etc would benefit from it ?
On way we could get around this here would be to implement the shouldComponentUpdate method and do a shallowCompare of the props.

Closing this actually as benefits would be hardly visible after a second thoughts...


Re-added find-clumpiness.

I have added submodules of the dependencies so I could relax the bounds. It builds against lts-8.20 so I assume the optparse-applicative issues are resolved.

Looks like this pulls in some dependencies that need updates:
QuickCheck-2.9.2 (Stackage upper bounds) is out of bounds for:
- [ ] BiobaseNewick-<IP_ADDRESS> (>=2.7 && < 2.9). No maintainer. @choener. Used by: library, test-suite
aeson-<IP_ADDRESS> (Adam Bergmark<EMAIL_ADDRESS>@bergmark) is out of bounds for:
- [ ] BiobaseNewick-<IP_ADDRESS> (>=0.8 && < 0.11). No maintainer. @choener. Used by: library, test-suite
base-<IP_ADDRESS> is out of bounds for:
- [ ] BiobaseNewick-<IP_ADDRESS> (>=4.7 && < 4.9). No maintainer. @choener. Used by: library, test-suite
- [ ] ForestStructures-<IP_ADDRESS> (>=4.7 && < 4.9). No maintainer. @choener. Used by: library, test-suite, benchmark
binary-<IP_ADDRESS> is out of bounds for:
- [ ] BiobaseNewick-<IP_ADDRESS> (==0.7.*). No maintainer. @choener. Used by: library, test-suite
criterion-<IP_ADDRESS> (Stackage upper bounds) is out of bounds for:
- [ ] ForestStructures-<IP_ADDRESS> (>=1.0.2 && < 1.1.1). No maintainer. @choener. Used by: benchmark
vector-<IP_ADDRESS> is out of bounds for:
- [ ] BiobaseNewick-<IP_ADDRESS> (>=0.10 && < 0.12). No maintainer. @choener. Used by: library
- [ ] ForestStructures-<IP_ADDRESS> (>=0.10 && < 0.12). No maintainer. @choener. Used by: library

Huh. That's because it's not looking in the deps/ for the updated versions of those libraries. I specified that in the stack.yaml, but if this pulls from Hackage then that may not be taken into account.

The stack.yaml isn't taken into account for stackage snapshots, it's the other way around, that stack.yamls take stackage snapshots into account :)

I see. I'm in the process of getting the bounds for ForestStructures and BiobaseNewick updated now.

Hackage has not yet updated ForestStructures and BiobaseNewick in https://github.com/haskell-infra/hackage-trustees/issues/107 so should this not have been merged yet?


Implementation of the full dichotomy theorem

Working on implementing the full dichotomy theorem. Implementing the algorithm version from [1]. Will need to be refactored and better tested later
[1] Gribkoff, E., Broeck, G. V. den & Suciu, D. Understanding the Complexity of Lifted Inference and Asymmetric Weighted Model Counting. arXiv:1405.3250 [cs] (2014).

Seems that's going good @tgy what's missing?


Added Truncator Benchmarks

Added benchmarks for ticket #30686
@carltongibson  -- Can I add this to your list? Aim is then to try and use the benchmark label on django/django

May be a bit much to add this permanently to the benchmark suite 🤷

Super. Thanks @smithdc1 — I will take a look next week! 👍

Just a short note to say I expect these benchmarks to show my current patch is much much slower (20x?!) for short truncations.
I've got a fix which will make it faster (2x?), but it needs more work to refine it.
So while I'd like it considering if these are suitable benchmarks. I need a bit more time to refine my proposed patch.
Something like asv continuous main [my prs commit hash] should show the diff.


NSM: Improve usefulness of NSM successful deployment notification

Enhancement Description
See https://github.com/layer5io/meshery/issues/474

@leecalcote I think this issue is solved now right?


Issues running this under dotnet core on macosx / linux

I've been trying to get this running on macosx/linux via dotnet core 3.1 without much luck. Is this expected to work cross-platform? or does it need platform dependent libraries from windows ?

ETW is a Windows-specific technology. Are you looking to analyze ETW files on Linux/macOS?

Exactly. I want to analyze the resulting .etl file in a macOS or linux environment. Is this possible?

I have the same requirement. It seems there is a dependency on a win32 assembly.
Unhandled exception. System.DllNotFoundException: Unable to load shared library 'advapi32.dll' or one of its dependencies. In order to help diagnose loading problems, consider setting the LD_DEBUG environment variable: libadvapi32.dll: cannot open shared object file: No such file or directory
   at ETW2JSON.Etw.OpenTrace(EVENT_TRACE_LOGFILEW& Logfile)
   at ETW2JSON.Program.ConvertToJson(Utf8JsonWriter jsonWriter, IEnumerable`1 inputFiles, Action`1 reportError) in /home/andre/aur/etw2json/src/ETW2JSON/Program.cs:line 40
   at ETW2JSON.Program.Main(String[] args) in /home/andre/aur/etw2json/src/ETW2JSON/Program.cs:line 116
Aborted (core dumped)

I guess this project is a wrapper around the Win native code that reads the ETW format. @mjsabby do you know of any alternatives around reading the ETW file format in purely managed code? Thanks!

@andreesteve @mcarlin Do you control the ETL file generation or you're getting it from random sources? If you can control the layout can be reverse engineered, but each ETL file (depending on OS, etc.) can change the format. In practice they don't, but it can change.
Is there a reason you need it to be ETL? We have a file format called BTL which ETL + Compression + Index files for fast seeking if you control the generation of the files.


User Story: Authentification only when needed

As a user I don't want to authenticate for a public repo / project board in order to minimize the amount of data I have to provide.

Hi!
We currently don't know to which extend the query-api is available without authentication, but due to rate-limiting, using the api unauthenticated will not be very pleasant (you are only allowed to make 60 Requests per hour, which is probably to little to fetch this board).
On top, Squello currently does not support read-only project boards (which is not a small feature) which would be required, because you can not make any changes to a board without signing in. Because of that, this story will not be implemented in this iteration.


Give an example in a react app

We have code snippets that should work just fine in react.
Another (slightly dated) react app example is:
https://github.com/iainnash/premint-camera-demo/tree/main/js_web


implement PyBuilder access to git describe

Backport of #564 for 0.11

Coverage decreased (-0.2%) to 72.137% when pulling 0db66a515404d7ade2a650f7a9cdc37c0d0431ee on esc:esc/backport-0.11.X/git_describe into 32dbbd54b5756130b2c862378568850907011743 on pybuilder:0.11.

Coverage decreased (-0.2%) to 72.137% when pulling 0db66a515404d7ade2a650f7a9cdc37c0d0431ee on esc:esc/backport-0.11.X/git_describe into 32dbbd54b5756130b2c862378568850907011743 on pybuilder:0.11.

Coverage decreased (-0.2%) to 72.137% when pulling 0db66a515404d7ade2a650f7a9cdc37c0d0431ee on esc:esc/backport-0.11.X/git_describe into 32dbbd54b5756130b2c862378568850907011743 on pybuilder:0.11.

Coverage decreased (-0.2%) to 72.137% when pulling 0db66a515404d7ade2a650f7a9cdc37c0d0431ee on esc:esc/backport-0.11.X/git_describe into 32dbbd54b5756130b2c862378568850907011743 on pybuilder:0.11.

After merging this, I tried to make a new 0.11.13 release, but the pybuilder-travis user referenced in the .travis.yml is no longer allowed to deploy pybuilder to PyPi :(

I uploaded it manually, using my account.

I will update 0.11 descriptor to match 0.12


chore: remove unused imports and update eslint config

The eslint rule @typescript-eslint/no-unused-vars is currently configured in a way that let's unused imports prefixed with underscore fall through
I reconfigured the rule and removed the few unused imports that fell through the cracks

Summary by CodeRabbit

New Features

Introduced a function to check for incompatible external configuration files, enhancing error handling and user feedback.
Added new components for improved modularity and functionality in the Nuxt framework.
Implemented a mechanism for setting compatibility dates during initialization, prompting users to update configurations if necessary.

Bug Fixes

Streamlined logging by removing unused references, improving the caching mechanism.

Documentation

Enhanced logging for warnings related to configuration files, providing clearer user guidance.

@coderabbitai your change summary for this PR is very much not on point.
The only notable change is:
Refactor:

Remove unused imports and variables starting with underscores

when a maintainer has pushed changes, next time, please do not force push on top of it 🙏

Sorry, I didn't change anything, I just got rid of the merge commit

no worries! I squash everything when merging into main, so it has a similar effect.


Improve processes graphql resource

resolve product to a product instance instead of id.
update filtering for graphql matching props.
remove unnecessary split of ProcessBaseSchema and ProcessGraphqlSchema.
return last_step in show_process for graphql.
update tests
update click to 8.1.6
bumpversion to 1.2.3rc4

Codecov Report

Merging #333 (7b57a14) into main (f7a5278) will decrease coverage by 0.11%.
The diff coverage is 83.33%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@            Coverage Diff             @@
##             main     #333      +/-   ##
==========================================
- Coverage   72.92%   72.82%   -0.11%
==========================================
  Files         178      178
  Lines        8531     8536       +5
  Branches     1369     1176     -193
==========================================
- Hits         6221     6216       -5
- Misses       2128     2141      +13
+ Partials      182      179       -3

Files Changed
Coverage Δ

orchestrator/db/filters/process.py
57.14% <ø> (ø)

orchestrator/graphql/resolvers/process.py
52.77% <0.00%> (-3.11%)
:arrow_down:

orchestrator/__init__.py
100.00% <100.00%> (ø)

orchestrator/graphql/schemas/process.py
89.53% <100.00%> (+0.12%)
:arrow_up:

orchestrator/utils/show_process.py
100.00% <100.00%> (ø)

... and 7 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Can i change the color of line for signal

I want to specify the color of line for signal,how to implement.
How do i do that.
Example:

Currently no.


Fixup GatewayAPI Roles

if we removed this from this file it will stop adding the extra kuadrant.io when we use the generator

Yes, that works. make manifests adds the right rules to the ClusterRole then.
I've included the PROJECT change


look for sample duration in thfd box and use that if sampleduration i…

…s not present in trun box

@schuettecarsten
I wonder if you are interested in try this on the content that you hit 'Unexpected, sampleDurationPresent must be present'.
Apparently my test contents don't have this so I just synthesized some.


bump dependencies

no issue

<EMAIL_ADDRESS>bump yarn.lock sub-dependencies

Coverage remained the same at 74.645% when pulling 42e519e746dcc49008800dac1fa235938d79300c on kevinansfield:dep-updates into ec789399106a6b865921c13cf132fdb71cf159ff on TryGhost:master.


Search on "udenlandske" fund ignores locality

"Kun udenlandske fund" in combination with any predefined (danish) locality, will give all non-danish records.

And "Includer udenlandske fund" in combination with a (danish) locality will give all records in the base.


update readme to mention new commands check and list.

Codecov Report

Merging #63 (695b291) into main (bc02edf) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main       #63   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            7         7
  Lines          146       146
=========================================
  Hits           146       146

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update bc02edf...695b291. Read the comment docs.


🐛 BUG: Neovim LSP client crash - missing prettier

Describe the Bug
Hello,
I'm a bit confused by what could be the issue here. Whenever I open a file with the .astro filetype the astro lsp crashes.
The error is as follows.
[ERROR][2023-06-05 21:24:03] .../vim/lsp/rpc.lua:734	"rpc"	"/Users/myuser/.local/share/nvim/mason/bin/astro-ls"
"stderr"	"node:internal/modules/cjs/loader:1078\n  throw err;\n  ^\n\nError: Cannot find module 'prettier'\nRequire stack:\n-
/Users/myuser/.local/share/nvim/mason/packages/astro-language-server/node_modules/@astrojs/language-server
/node_modules/volar-service-prettier/out/index.js\n- /Users/myuser/.local/share/nvim/mason/packages/astro-language-server
<EMAIL_ADDRESS>/Users/myuser/.local/share/nvim/mason/packages
<EMAIL_ADDRESS>/Users/myuser/.local/share/nvim/mason
<EMAIL_ADDRESS>  at Module._resolveFilename
 (node:internal/modules/cjs/loader:1075:15)\n    at Module._load (node:internal/modules/cjs/loader:920:27)\n    at Module.require
(node:internal/modules/cjs/loader:1141:19)\n    at require (node:internal/modules/cjs/helpers:110:18)\n    at Object.<anonymous>
(/Users/myuser/.local/share/nvim/mason/packages/astro-language-server/node_modules/@astrojs/language-server
/node_modules/volar-service-prettier/out/index.js:3:20)\n    at Module._compile (node:internal/modules/cjs/loader:1254:14)\n    at
Module._extensions..js (node:internal/modules/cjs/loader:1308:10)\n    at Module.load (node:internal/modules
/cjs/loader:1117:32)\n    at Module._load (node:internal/modules/cjs/loader:958:12)\n    at Module.require (node:internal/modules
/cjs/loader:1141:19) {\n  code: 'MODULE_NOT_FOUND',\n  requireStack: [\n    '/Users/myuser/.local/share/nvim/mason/packages
/astro-language-server/node_modules/@astrojs/language-server/node_modules/volar-service-prettier/out/index.js',\n    '/Users
/myuser/.local/share/nvim/mason/packages/astro-language-server/node_modules/@astrojs/language-server
/dist/languageServerPlugin.js',\n    '/Users/myuser/.local/share/nvim/mason/packages/astro-language-server/node_modules
/@astrojs/language-server/dist/nodeServer.js',\n    '/Users/myuser/.local/share/nvim/mason/packages/astro-language-server
<EMAIL_ADDRESS>]\n}\n\nNode.js v18.16.0\n"

Steps I've taken to solve the issue.

prettier is available in my $PATH.
prettier is installed through mason as well.
prettier is installed in my project as a dev dependency.
i have a .prettierrc with

	"plugins": [
		"prettier-plugin-astro",
		"prettier-plugin-svelte",
		"prettier-plugin-tailwindcss"
	],

and a package.json with
	"devDependencies": {
		"prettier": "^2.8.8",
		"prettier-plugin-astro": "^0.10.0",
		"prettier-plugin-svelte": "^2.10.1",
		"prettier-plugin-tailwindcss": "^0.3.0",

Does anyone have an idea what I'm possibly missing here? And if this is a language server issue or if I should take this up somewhere else? The lsp actually worked fine until version 2.0.0 hit the wire, so im trying to understand where it's trying to source prettier from and failing.
Much appreciated.
Steps to Reproduce
pnpm create astro@latest

Installing prettier-plugin-astro inside ~/.local/share/nvim/mason/packages/astro-language-server worked for me.

This is an upstream issue (well, not really, but the proper fix is an upstream one): https://github.com/volarjs/services/issues/39


Add license information ...

Bump.

Sorry for the delay, solved here https://github.com/grongor/knock/commit/b9e4e0f841c777ca92631b2055c575fae03ee755


The Aggregators are dead, long live the Handlers

Description
In order to improve the maintainability and readability of the codebase, I want to delete the Aggregators project and any references to it from the Consumers (WebAPI and CLI). The pre work for this is done as part of #243 where the business logic present in the Aggregators was migrated to Handlers.
Acceptance Criteria

[x] No references to Aggregators exist from WebApi & CLI.
[x] Aggregator project is deleted
[x] Unit Tests are completed, and the code passes tests
[x] Documentation is updated, including Architecture diagrams, if needed

Dependencies
Task List

[ ] List of tasks (punch list) needed to complete the user story

Sprint-Ready Checklist

[ ] Acceptance criteria defined
[ ] Acceptance criteria are verifiable/testable
[ ] External / 3rd Party dependencies identified
[ ] Engineering team understands acceptance criteria
[ ] Is the user story small enough to be implemented in a short amount of time, but large enough to provide value?

PR Green-Software-Foundation/carbon-aware-sdk#276


About freeze_model

Hello, I a question about the function 'freeze_model'. I cannot find this function in utils module，I don't know where it is? Could you please provide the code of 'freeze_model' or the location, Thank you

Sorry, it is my fault, I have found it...


License detection from build.gradle

Type of change

New feature (non-breaking change which adds functionality)

Description
Checklist

+1


chore(docs): Update How to Oracles

Description
Updates the code examples in the how-to so that it works. I tested this with version 0.32, but I assume it didn't change from 0.31 to 0.32 so am updating that as well.
Problem*
Resolves https://github.com/AztecProtocol/dev-rel/issues/282
Summary*
Additional Context
Documentation*
Check one:

[ ] No documentation needed.
[x] Documentation included in this PR.
[ ] [For Experimental Features] Documentation to be submitted in a separate PR.

PR Checklist*

[x] I have tested the changes locally.
[ ] I have formatted the changes with Prettier and/or cargo fmt on default settings.

Can we avoid having large segments of code just in markdown? We added snippet functionality specifically in order to avoid potential for docs to become stale like this.
We can instead have these examples in code which is tested in CI and then pull snippets into the docs

Can we avoid having large segments of code just in markdown?

Great if we could document how to make use of codegen: https://github.com/noir-lang/noir/issues/4940

This doesn't rely on codegen but the snippet workflow.
Codegen is in the "forget" stage of "set and forget" anyhow.

Yes I can update it

@TomAFrench this example code requires running an json rpc server in js. do we have any examples of how to approach this? Should it be added in examples/?

i am going to merge the updates since they are working and the current published docs are not. we can revisit fully testing and pulling in snippets in another pr


NSM CI in Google Cloud Engine (GCE)

Cross-Cloud CI runs on multiple clouds, including most GCE.  We should be able to take advantage of that to extend NSM testing to GCE.
Good followup to #316

#844 is merged


translation suggestion

I wish I could help translating kinoko into Brazilian Portuguese.

The project is on some translation platform like crowdin

I have not used a platform for translation, just the flutter localization system. All the localization files are lie in https://github.com/gsioteam/kinoko/tree/master/assets/languages.
You could new a YAML named pt-br.yaml or else, after the translation is done I will add it to settings page.

https://mega.nz/file/0F10CY4K#T39KpH0bC0XqRrF4u0Y-4vdOghFN6vRE-f0zn8PhcFo

link with the file

https://mega.nz/file/hAl2QTIJ#x03esqnF6U1RqRZR1WVuFY2O1N_1zrlegiBv7DWDpKY

@Luiz-bro thanks a lot. I will add it to project.

@Luiz-bro And I forgot to tell there are 3 another instruction files need to be translated, I have translate they through google translate. If you have time, please point out the translation errors.
https://github.com/gsioteam/kinoko/blob/master/assets/download/pt-br.md
https://github.com/gsioteam/kinoko/blob/master/assets/fav/pt-br.md
https://github.com/gsioteam/kinoko/blob/master/assets/picture/pt-br.md


Addressing several WebSocket bugs

WinHttp request error not correctly handled when a disconnect isn't acknowledged by the server
Fixes race condition between WebSocket disconnect event handler invocation and unregistration when closing a WebSocket handle
HCWebSocketConnectAsync will now pass back the client's WebSocket handle in the XAsync result rather than an internal handle

@jplafonta , many thanks for fixing all three so quickly. Will it be included in the next GDK release?


Add Progressive Web App (PWA) capabilities

Turns the news hub into a progressive web app (PWA). A few benefits:

Prefetch files for less loading times
Enable users to 'install' the application

Sources

https://fredrickb.com/2019/07/25/turning-jekyll-site-into-a-progressive-web-app/
https://www.pwabuilder.com/
https://w3c.github.io/manifest/#id-member

See also: https://github.com/Garanas/Newshub/commit/a12bcffd3ec8534d56a4181676428d135483def3


fix fix cloud autobucket num

BUG:  when calculate auto bucket num,  it will use function 'getBucketsNumByBEDisks' to calculate all backend left free disk sizes. But in cloud mode,  each backend's left disk size is not a right value, it's always equals 1.  So cloud auto bucket need to exclude this factor.
Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run cloud_p1


Recipe for new rt-app

Latest rt-app supports NUMA memory binding:
https://github.com/scheduler-tools/rt-app/blob/b3a5408c6d9f7eeb1b91d8286757cbd38fefa9cb/doc/tutorial.txt#L287

@douglas-raillard-arm , can you please review this PR ?

Hi @PeterPuhov , it's still in legal limbo, I'll ping them to see where it goes. Sorry for the delay

Hi @PeterPuhov , the legal aspect has finally be sorted out.
I tried building rt-app and stumbled on that error:
make[2]: Entering directory '/tmp/tmpf2v984g_/arm64/rt-app/src'
aarch64-linux-gnu-gcc -DHAVE_CONFIG_H -I.  -I./../libdl/   -I/tmp/tmpf2v984g_/arm64 -MT rt-app_utils.o -MD -MP -MF .deps/rt-app_utils.Tpo -c -o rt-app_utils.o rt-app_utils.c
In file included from rt-app_utils.h:29:0,
                 from rt-app_utils.c:29:
rt-app_types.h:30:10: fatal error: numa.h: No such file or directory
 #include <numa.h>
          ^~~~~~~~
compilation terminated.
Makefile:487: recipe for target 'rt-app_utils.o' failed

Could you ensure that rt-app builds in the "standard" build environment of LISA, which is:

Create a clean vagrant VM and enter it as described here:
https://lisa-linux-integrated-system-analysis.readthedocs.io/en/master/setup.html#virtual-machine-installation

run lisa-build-asset rt-app and commit the output to update the binaries.

This way we can ensure some level of easy reproducibility for building binaries we ship.

I will make sure rt-app builds in clean vagrant VM

@PeterPuhov-Linaro everything worked on my side, you can just squash the fixup commits in the PR and I'll merge it.


Astrometry Stats + refactor

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

136 of 161 (84.47%)  changed or added relevant lines in 8 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.1%) to 82.469%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

mirar/processors/photcal.py
24
26
92.31%

mirar/catalog/base_catalog.py
6
11
54.55%

mirar/processors/astrometry/validate.py
19
37
51.35%

Totals

Change from base Build<PHONE_NUMBER>:
-0.1%

Covered Lines:
8129

Relevant Lines:
9857

💛  - Coveralls


Support for path string substitutions

I'll start with a scenario.
Suppose we have multiple regional registries in a GCP although this works for a number of other scanarios.
Say we have a whole range of app images in these repos but lets say we have 'appa' built and common to all registries and we want clusters to pull from their own regional locations.
Currently this might need an image path like.
europe-docker.pkg.dev/projectname/europe-registry-name/appa:tag
us-docker.pkg.dev/projectname/us-registry-name/appa:tag
europe-west2.pkg.dev/projectname/london-registry-name/appa:tag

This means that development teams need to alter their deployments for regional clusters to have specific image sources.
The proposal would be that an arbitrary strings could be established for replacement, a source and a destination so that we could contrive a configuration as follows using a standard image name.
Assuming our source for string replacement is then 'logical-registry' we could state the image to be...
logical-registry/appa:tag

and this would be the same for all regions but we would specify targets in regional clusters matching the paths for their most adjacent registries i.e.
europe-docker.pkg.dev/projectname/europe-registry-name - for European
us-docker.pkg.dev/projectname/us-registry-name - for US
europe-west2.pkg.dev/projectname/london-registry-name - for London

Then at mutate time these strings could be substituted prior to performing the next part of the mutation to determine the image sha.
It's feasible to use another webhook to do this, however, I am not sure at this stage that naming the webhooks alphabetically so that they operate mutation in a specific order is something that can be relied on in the longer term. I know it's practice, however, I can't see anything official that it's a standard that will be maintained.
If we did take that approach though looking at off the shelf solutions doesn't quite tick the mark, for example OPA Gatekeeper (and hence Anthos Policy Controller) only supports replacement of the domain part or the WHOLE path part including the image name - this cannot be coerced by putting a path into the domain part because of regex checks in the mutation code.
It would seem to be a request that isn't 100% aligned with digester, however, the question regarding the long term viability of applying mutations in a set order is disuading me from writing a new webhook to do this before checking here as this is a trivial change for digester and I would be happy to submit an MR including tests and documentation if it was of interest.
I chose to focus upon simple string replacement because my use case may not be quite what everybody else has and this could cater for other use cases for other users.

Thanks @iamasmith  for submitting the idea and for the detailed explanation!
Wouldn't this be better handled on the client side, before sending the manifests to the cluster? E.g., using a Kustomize image transformer or a kpt setter. There may be other values that also need to change with different regions, e.g., endpoints for external dependencies such as caches, databases, other upstream services, etc. Orchestrating all changes client-side would likely lead to less confusion.
Regarding multiple webhooks and invocation order, k8s-digester sets reinvocationPolicy: IfNeeded and failurePolicy: Ignore in the MutatingWebhookConfiguration, so it should add the image digest regardless of invocation order. Worst case scenario it'll perform two registry lookups, where the first may fail if the placeholder image name doesn't exist.

@halvards thanks for the fast response, I need to dig in further on this as the request came proxy via a head of department for this ask.
They had been in conversation with a software architect who did not want to have to change image or anything else for the group of services that they govern and wanted to establish a working pattern to avoid changes like this. It's not necessarily right and pushes complexity elsewhere - often increasing it and we have scemarios where we have had to use mesh technologies to remap services so they are named identically between environments but actually go to different data sources, be they regional or development services rather than factoring in parameters to the deployment to cover these regional differences off.
It feels like they are perceiving the extra pipeline complexity is something that they are trying to avoid and possibly because in context there are over a thousand different services in our stack that are being rapidly moved to the cloud environment - the software changes are not difficult but the teams have relied on on premises services teams to make those deployments similar.
It may be the wrong answer to cater for this in the way I mentioned vs handle it at source in kustomize or other tooling but it may also be something that as a team we are asked to provide.
wrt the failurePolicy: Ignore, we have this set to fail to avoid this https://github.com/google/k8s-digester/issues/25 which we enountered so reinvocation would require us to change that but as the estate grows rapidly then this also means that we'll have to add specific monitoring checks to look for this kind of runaway behaviour - we just find it safer to fail the deploy completely if the webhook response ever fails.

Let me know when you have more context. If you have questions outside of the specifics of k8s-digester that are easier to discuss via email, my work email address is visible on my profile page.


Linter fixes and improvements

add  es-linter checks
Add CI checks for linter

You may merge this into Kevin's branch whenever you are ready.


How to render different components while keeping the header and drawer constant?

So, I have an App which has a header and a drawer. Now, apart from that, I have a Content component that renders some thing on the page. How can I use curi to render different components inside that Content based on what was clicked in Drawer?
This is how my App looks like:
ReactDOM.render((
    <MuiThemeProvider theme={theme}>
      <Router>
        {
            ({ response }) => {
              const { body:Body } = response;
              return (
              <Body response={response} />
              );
            }
        }
      </Router>
    </MuiThemeProvider>
  ), document.getElementById('root'));

And I have somed direct routes in routes.js. The problem is: If I add a children route to, let's say the Home route, the entire page only displays the components I write inside that Route. (i.e., the Header and the drawer obviously disappear.)
This is how I'd do it with React-Router:
<HashRouter>
  <Switch>
    <Route
      exact
      path={match.path}
      component={Messages}
    />
    <Route
      exact
      path={`${match.path}/:message`}
      component={Message}
    />
  </Switch>
</HashRouter>

Hey @abhisheksoni27. Do you want the Header and Drawer to be the same for every single route and only vary the Content (or Body in this case)? To do that, you can render those in the render-invoked function. I think of that function as the root of the app's layout.
ReactDOM.render((
    <MuiThemeProvider theme={theme}>
      <Router>
        {
            ({ response }) => {
              const { body:Body } = response;
              return (
                <React.Fragment>
                  <Header />
                  <Drawer />
                  <Body response={response} />
                </React.Fragment>
              );
            }
        }
      </Router>
    </MuiThemeProvider>
  ), document.getElementById('root'));

There is a slightly more advanced use case, too, where you can attach multiple components to response.body. This is useful if you have multiple sections of the page that vary based on the route. For example, you might have different headers based on the route, in addition to the content. You can see an example of what I am talking about here: https://curi.js.org/examples/react/multi-body/.

Err, I just re-read your question and realize that I may have misinterpreted your question, but I think that my example code should still help. Please let me know if I'm completely off from what you are trying to do.

Actually, your explanation was exactly what was required to answer my question. That worked like a charm Thank you so much, and great library! :+1:


Mark Cilium etcd operator as deprecated

It's still mentioned in
https://docs.cilium.io/en/v1.9/gettingstarted/k8s-install-etcd-operator/
and
https://docs.cilium.io/en/v1.9/gettingstarted/clustermesh/#gs-clustermesh
etcd-operator is replaced with with CRD-only mode and with the newly introduced cluster API.

@aanm Should we add a warning in the documentation stating it's deprecated for now, or should we just remove all documentation on etcd-operator?

@pchaigno we can remove all documentation regarding cilium-etcd-operator but we can only do it once we have clustermesh-apiserver documentation

We will also need to think about migration.

Is external etcd (https://docs.cilium.io/en/v1.9/gettingstarted/k8s-install-external-etcd/) still supported or also to be deprecated? With either or both identity allocation modes?

From Cilium community meeting:
Mark etcd-operator as deprecated for v1.10, but do not remove the underlying infrastructure yet. This will allow users to find out about the deprecation and plan for its removal.


Left(Right) Analog Stick X+Y added to Rotary Encoders Control Mode.

I would like to use a rotary encoder to play Forgotten Wolrds(Capcpm Arcade Stadium).
In the current setup, I have one analog stick x-axis and one analog stick y-axis each controlling one of them,
but I want it to be mapped on the circumference by controlling the x-axis and y-axis of the analog stick at the same time.

Hi @irorichan ,
I had to grab a copy of the game to see how they implemented the spinner.  On the Switch version its either mapped to an absolute analog value (where the rotation stops based on your analog position), or, more true to how the original worked where there is a free-spin that simply rotates either clockwise or counterclockwise.
What I would recommend you do is map it as left and right trigger in the web-config options under rotary encoder and then switch the config in game to be the same.
This will make it feel more like the original.


Setting sliders have no effect

Not sure if prompt issue is related: https://github.com/mattyamonaca/PBRemTools/issues/9
Do sliders only cause effects if the prompts work? If so, then the issue is probably just caused by 9, otherwise there might be a problem with slider parameters as well. Screenshots below.
Ideally was hoping to fine tune accuracy of cutout around feet:

Output same every time regardless:

EDIT: Original img for reference:

Same for me.


Lazy Loading

I'd be nice to have the content loading lazily - meaning only the views on screen (or views that are about to be on screen) will be rendered.
Tasks

Is lazy loading possible using Layout protocol?
If so, how can MasonryStack adapt lazy loading?
Any other considerations?

Let me know if you want to take on this issue by commenting below.

I implemented a similar solution with help from here - https://stackoverflow.com/questions/66101176/how-could-i-use-a-swiftui-lazyvgrid-to-create-a-staggered-grid
I was on the lookout for such solution for very long time and it looks like the solution was super easy in the end.

@PankajGaikar The problem with this approach is, that it doesn't conform to the Layout protocol which is a nice-to-have when you want to have different layouts in specific contexts or want to allow the user to switch between different layouts.

As workaround I've tried using the following code and views are being rendered lazily. But it would be better if library offers this feature.
 MasonryVStack {
    ForEach(array) { item in
        LazyVStack {
            ItemView(item)
        }
    }
}


[RFE][microceph] Add support for clean-up routine

To add a clean-up routine for microceph fixture, and optionally, a keep-microceph option.

Hi @carlcsaposs-canonical the value is to not leave it in your own machine when you run your tests locally. We can leave --keep-microceph as a default in CI, but we def. need an option when we are running our tests on our own.


STORM-3673 convert Builtin metrics to use V2 API

What is the purpose of the change
Executor builtin metrics used deprecated metrics API.  This converts them to use the current API.
How was the change tested
Ran unit tests and ran a topology on a cluster and validated metrics seem sane.
V2 metric replacement:
CountStatAndMetric is replaced with WindowedMeter for counts.
LatencyStatAndMetric is replaced with WindowedHistogram for latencies.
The windowing code in these seems like it could be cleaned up and commonized, but I based it on the existing code for now.  I also simplified the synchronization.
TaskMetrics seem to have been a half-hearted attempt at adding v2 metrics.  They are superceded by the other metrics added in this change.
There can be duplicate short metric names created for a given task id due to having multiple component/stream combinations.  As an example, a v1 metric for a task could be:
__ack-count = {$mastercoord-bg0:$batch=100, $mastercoord-bg0:$success=140}]
For v2, I didn't see a way to easily support multiple metrics like this and allow a non-duplicate metric short metric name.  To work around this, I appended the component and stream to the metric name. The v2 metric names for that v1 example are:
__ack-count-$mastercoord-bg0:$batch and __ack-count-$mastercoord-bg0:$success

I'm not sure what backwards compatibility concern you're worried about.

I'm not sure what backwards compatibility concern you're worried about.

Sorry for not being clear. What I meant is with this change, the metrics are changed from
for example
__acked-count: {stream1: 2, stream2: 3}

to
__acker-count-upstreamComp:stream1.m1_rate,
__acker-count-upstreamComp:stream1.m5_rate
...

I guess it is acceptable since it is only the metrics. Otherwise we need to record the same metrics for V1 and V2 format in the same time, which adds a lot of overhead.  At least the Java api is preserved for older topologies.
But we need to update  https://github.com/apache/storm/blob/master/docs/Metrics.md#tuple-counting-metrics to reflect the format change.

opening a different solution/PR


Is there a way to remove the tick marks?

For example, I would like to keep the dates (e.g. "2013-01-02") but not the small vertical tick mark ("|") above each one.

Setting axis.x.tick.width to 0 does not seem to fix this issue.
Thanks for your help.

https://github.com/masayuki0812/c3/commit/89ee5145d66c97f235f8443146669c491556846a

https://github.com/mbostock/d3/wiki/SVG-Axes

Sorry, I should've used the Google Group.  Thanks for the link @gordol.

Also, just to close this:
CSS:
.c3-axis .tick line {display: none;}


Allow unsupported length units to be used

This PR adds support to allow valid CSS length units to be passed through the parser.
The supported units are based on the list in MDN:
https://developer.mozilla.org/en-US/docs/Web/CSS/length
Why?
I'm planning on adding support for CSS viewport units to React Native. Viewport units need to be parsed to pixels at runtime, so I need the raw value from the parser, e.g. 20vw.
Currently css-to-react-native only supports parsing values with pixels and throws for any other unit. By removing that restriction we can allow valid CSS units and let React Native throw an error if the unit is not supported.
By allowing the use of other CSS length units, anyone who uses this parser can easily build custom support for other units in react-native, e.g. rem unit.
ping @jacobp100

Is it easier to just modify length to allow the extra units?

Is it easier to just modify length to allow the extra units?

LENGTH token type converts the unit to number (LENGTH: regExpToken(lengthRe, Number)), I can not use the same token type.
I thought about using the same regex, but I decided to make a separate regex to make it clear in the code that those units are not supported and that the LENGTH token type only parses pixel values.
I can combine the regexes if you think that it's better that way.

Cool! As an idea, we could extend the transform function for a token to pass in the entire match, then have length universally support all units.
But that also might be something we don’t want. Your call—I’m happy either way!

We should probably go with what is easiest to understand for someone who reads the code.
The good thing about my current approach is that it makes a clear separation between what is supported by the parser and what is not. The good thing about your suggestion is that it would simplify the code as we would not have to pass the 2 token types around.

Good points! Let’s do this!

@jacobp100 Thanks! Could you also do a new release with these changes?

Published now. Sorry for the delay :)

Thanks a lot!


Implement retry spec in task spec and retry logic in the workflow conductor (WIP)

Abstract
I added an implementation for the feature of retry which is mentioned in #118 by making the use of the nick's work (c.f. #171).
Changing points
The are the main changing points of implementation for retry feature in Conductor.

Added parameters for task_state_entry to keep these information

retry.count: how many times the target task was executed already
retry.running_time: how long target task should wait for retrying next time when 'delay' parameter was specified

Added processing that makes task scheduling delayed when it is ordered to be waited in the get_next_tasks method.

Added processing to select whether target task would be retry or not in the update_task_state method.

Note
This doesn't implement feature of infinity retry processing intensionally because this is middle of controversial discussion (c.f. https://github.com/StackStorm/orquesta/issues/118#issuecomment-513106400).
Execution results
Here is an example action definition to show how it works.
metadata
---
name: retry_test
pack: default
description: A workflow for testing retry feature of orquesta
runner_type: orquesta
entry_point: workflows/retry_test.yaml
enabled: true
parameters:
  count:
    type: integer
    default: 1
  delay:
    type: integer
    default: 0
  msg:
    type: string
    default: ""

workflow
version: 1.0

input:
  - count
  - delay
  - msg

tasks:
  task:
    action: slack.post_message
    input:
      message: '[<% now().format("%Y-%m-%d %H:%M:%S") %>] <% ctx(msg) %>'
    retry:
      when: <% succeeded() %>
      count: <% ctx(count) %>
      delay: <% ctx(delay) %>

They are execution results, left-side is run above action without delay parameter and right-side is another one with delay parameter. They were run almost at the same time, and we could confirm that task would be retried for specified times at 'count' parameter and delayed to be scheduled for specified seconds at 'delay' parameter.

Codecov Report

Merging #180 into master will increase coverage by 0.34%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #180      +/-   ##
==========================================
+ Coverage   94.01%   94.36%   +0.34%
==========================================
  Files          40       40
  Lines        2474     2501      +27
  Branches      473      479       +6
==========================================
+ Hits         2326     2360      +34
+ Misses         89       84       -5
+ Partials       59       57       -2

Impacted Files
Coverage Δ

orquesta/specs/native/v1/models.py
97.95% <100%> (+0.03%)
:arrow_up:

orquesta/conducting.py
93.77% <100%> (+0.26%)
:arrow_up:

orquesta/specs/types.py
100% <100%> (ø)
:arrow_up:

orquesta/utils/strings.py
100% <0%> (+38.88%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e6ebbbe...6da8f1d. Read the comment docs.

Great stuff, thanks for contribution and effort to continue this highly useful feature implementation!
I'll let @m4dcoder to take a look at it closer.

@nmaludy Are you and @userlocalhost working together on the Retry spec?  There's already a WIP PR for Retry at https://github.com/StackStorm/orquesta/pull/171.  That PR is also mentioned here.

Thank you for confirming that. This PR inherits the change of #171 (which adds spec for Retry to TaskSpec). I added an implementation of its feature in the conductor processing.
Sorry for making you confused, because I made another PR for same feature. I guess I should have made a PR to nick's branch not to make another one.
Before starting this work, I consulted nick about whether I can take over the rest of his work in the #community channel. And I engaged in this work by getting his consent.

Would you please review it, @m4docker?

@userlocalhost Got it! Thank you for picking up this work. I did review this. I will post my comments on this shortly today.

Thank you very much for your review in detail. All of the points that I should correct are clear by your comments.
About the changes in the update_task_state method, I will make this change simple by taking into account a new state transition for retry.
And for the processing of delay, I should be able to offload this processing to workflow-engine or action runner.
I didn't understand what each processes and components should dedicate in until I got your review. I could understand that Orquesta is just "controller" to indicate what task(s) should be run next, to the "processor" which dedicate to run it. So, the processing to wait until the time is not entitle to set on the controller, but the processor.
But, I'm not sure exactly where that delay processing should be set in the processor yet, I think this should be set on somewhere before running action in an action runner process, so far.
I was wondering if you could give me some advice about it after fixing these changes.

If I understand you correctly, you don't need to worry how StackStorm process the delay.  This is already implemented.  When you setup the task dict for staging, you just need to add a KVP for delay and make sure the task dict returned from get_next_tasks has the delay key set.

Thank you for giving important advice. I could understand where I should fix on orquesta for making delay by seeing the implementation of request_task_execution.
I plan on dealing with it within a few days.

The last commit refactored following points.

Eliminated sleep processing and specified delay parameter to order workflow engine to make task delayed.
Encapsulated task-retry processing to TaskState instance, to be able to retry task transparently by calling update_task_state method without changing that implementation.

And following is an execution results of refactored processing. I could confirm that both delay and count parameters are worked.

I'll add some changes to increase code coverage of this change, so I amended PR title as 'WIP'.

I fixed what you mentioned. Would you please review it, @m4dcoder ?

@userlocalhost Yeah, I see the changes. Thank you. I'll review it sometime this week.

@userlocalhost I want to let you know that I started reviewing this PR. There is some nice idea with TaskState. But there are also concerns.  I'm still thinking through this so please be patient. Thanks.

@m4dcoder Thank you for your review. Don't worry about it. I'm happy to fix!

Thank you very much for your minute review, @m4dcoder.
I could understand what I should fix, and also realized my previous fixing was halfway measures to implement this feature.
I shouldn't have focused on being less change of current implementation at the expense of maintainability.
And I’m sorry for taking up your time because of my inadequate implementation which doesn't act on principle of task state machine (especially, the change to alter task state outside of the task state transition processing using WORKFLOW_STATE_MACHINE_DATA).
I'll fix it to be careful of keeping this consistent system.

I refactored the implementation of task retry feature. Would you please review it again, @m4dcoder ?
Following are major changing points from last commit.
1. Reverted data-structure of task_state_entry as dict from TaskState class.
Followings are reasons of this change.

Classification of this data-structure is not essential of this feature. At first time, I thought that classifying attitudes of task_state would increase the maintainability of this code. But I realized that feature would be realized by just adding few related attribute.
Classification of this data-structure requires big effort. This is valuable for increasing maintainability and expandability of this code, I think. But this change may cover a lot of ground. I want to tackle of this work as another task.

2. Implemented the processing to change status of task using state transition system of TaskStateMachine.
Previous implementation I made change task status by attached processing after state transition. It was foreign matter that should be get rid of, because it didn't act on the principle of state transition in the orquesta.
3. Making a restriction for when parameter of retry spec, that parameter accepts only either "succeeded" or "failed".
Mostly, user specifies when: <% failed() %> for retrying task when it is failed, I think. But it has implementing constraint, that both <% succeeded() %> and <% failed() %> expressions are evaluated as expected on the basis of the status after changing. In other words, orquesta can't determine whether task should be retried before task is failed or succeeded as long as using this expression.
By this constraint, I had no choice but to implement retrying task after task was transitioned (but this is a bad choice as mentioned above). This is because the evaluation results of these expressions are determined dynamically. On the other hand, condition of retrying task can be specified statically (e.g. retrying task when it is failed (or succeeded)).
So, I changed TaskRetrySpec to accept only statical condition (failed or succeeded). By this change, we are free from that implementing constraint and the implementation of retrying feature would be simple.

Sorry I realized the lack of consideration about the retry feature when the workflow was abandoned.
Once some problems were happened at a workflow processing, orquesta would change status of workflow and all tasks to statuses.FAILED. But in the PR implementation, task's status would be still "running" when retry condition would be satisfied.
I should be able to handle in this case, so I changed PR title as WIP.

I changed following in addition to https://github.com/StackStorm/orquesta/pull/180#issuecomment-550905638, after the last review.
Once again, would you please review this, @m4dcoder ?

4. Added a function and condition to prevent retrying task even though its condition was satisfied when workflow was aborted.
I checked the implementation of request_workflow_status carefully abount whether a task which has retry statement would be retried when workflow is aborted like here. I understood that calling conductor.request_workflow_status(statuses.FAILED) would never affect status of each tasks.
And I also think, task should not be retried any more after the workflow is aborted. So I added a function to exhaust retry_count not to do it, and condition not to set valid retry_count in this case.

@userlocalhost Ack. I will review your changes this week. Thank you for your diligence here. This is a much requested feature that the community will appreciate.

Sorry, I realized that I took serious mistake about the spec of inflexible retry condition. This PR wouldn't be satisfied with functional requirement and consistency.
Originally, orquesta allows to specify flexible condition of task transition as is mentioned https://github.com/StackStorm/orquesta/issues/118#issuecomment-457400742.
That indicates that retry condition also should be able to specify flexible one.
But the following implementation (c.f. https://github.com/StackStorm/orquesta/pull/180#issuecomment-550905638) of my last commit is adverse to it.

Making a restriction for when parameter of retry spec, that parameter accepts only either "succeeded" or "failed".

Sorry for asking for review with wrong implementation again and again.
I should be able to fix it comply with task transition principle in orquesta this time.

@userlocalhost Yeah, I saw that. No worries. I've been reviewing and I'm currently refactoring the PR since we've been back and forth with this PR for awhile.

The last commit fixes TaskRetrySpec and the implementation of TaskStateMachine to be able to specify flexible retry condition as well as being consistent with other specs.
That is realized by following changes.

Fixed input spec of 'when' parameter in the TaskRetrySpec, which describes task retry condition, to be able to specify flexible condition that is same as others (e.g. TaskTransitionSpec).
Refactored processing for task retry in the TaskStateMachine. The fixed processing recalls the method of TaskStateMachine to transit task state and attach context of retrying when task state and results match with retry condition.

Would you please review this, @m4dcoder?

Just in case, I show an execution result of following workflow using the orquesta which is deployed by last commit in this PR branch (That is NOT different from previous ones).
version: 1.0

input:
  - count
  - delay
  - msg

tasks:
  task:
    action: slack.post_message
    input:
      message: '[<% now().format("%Y-%m-%d %H:%M:%S") %>] <% ctx(msg) %>'
    retry:
      when: <% succeeded() %>
      count: <% ctx(count) %>
      delay: <% ctx(delay) %>

@userlocalhost After review this PR a few times, I decided to take the responsibility to refactor the PR here. Otherwise, we would still be going back and forth with the changes here. I commend you on your previous attempts. There are multiple ways to implement the retry in the workflow conductor.  This latest iteration is just a representation of what I believe is the simplest approach and staying consistent with the current design within minimal changes to interfaces.
The workflow conductor here is responsible for evaluating whether a task needs to be retried. The retry evaluation takes place only after the new task status is determined by the task state machine. This is required because the retry when expression is generic and is not known at design time of the conductor and the expression may look at the task status and/or task result to determine if a retry is required. When a retry is required, the conductor will post a task retry event to the task state machine which will set the task status to retrying, which then tally the retry and sets up the task to be returned by get_next_tasks.
Another consideration why I made the change here is that our previous thought about letting the state machines make the decision didn't quite work out as we expected. In the last iteration, we end up having to pass the will_retry decision explicitly anyway from the conductor and the conductor has to look at the returned altered event to determine if a retry is required.
Anyway, this retry feature is not a trivial change and requires some experimentation.  I appreciate your efforts here. Thank you for your hard work.

@m4dcoder
Thank you very much for your help. And I apologize I couldn't come up to your expectation.
I feel a little bit regretful at myself not to be able to finish up this work for myself, but I also feel excited because it was very good experience for me, that I could learn about internal of orquesta and interaction with st2workflow.
And I believe my understanding about the philosophy of orquesta would be better by catching up with your work.
Finally, I really appreciate your comments. Your advice always makes me motivated. I couldn't have come this far without your support.
I continue to be involved with this community. And I hope to be able to make a contribution someday in the future.
Thanks,

@userlocalhost We appreciate user feedback and contribution.  There's no expectation that needed to be met. This feature requires trial and error and experimentation. We are trying to come up with the best approach. Your previous attempts helped us quite a lot and tells us what we can or cannot do.  It's a job well done.  I just didn't want to drag this PR for too long and discourage you.  So I'm glad to hear that you will continue to look for the next opportunity to contribute.

Required StackStorm update and integration tests at https://github.com/StackStorm/st2/pull/4833.


Enhancement: Add ComparisonConfig.CompareBackingFields

I want to share a problem that I have encountered while using this tool.
I will be brief, I noticed that I have a special case at work when using your library, which is the need to ignore ComparisonConfig.CompareBackingFields especially in the case of auto properties of lists (list, hashset, array, etc.), which affects the performance.
For this, I would like to propose this improvement in favor of flexibility and improved performance by adding a separate configuration of backing fields in config.
I already implemented this functionality in fork, so I'm ready to create a pull request.
Open for discussion on this topic.

Sorry for the late response.  My father passed away recently and I am catching up.  So when CompareBackingFields is set to false, what exactly is ignored from the comparison?

I am so very sorry for your loss.
When ComparePrivateFields=false, no private field is compared.
When ComparePrivateFields=true and CompareBackingFields=true, all private fields are compared.
When ComparePrivateFields=true and CompareBackingFields=false, only the private fields declared by the programmer and not the compiler are compared. Backing field is a private field generated by the compiler for the auto-property. For example, for the PropName property a private field named <PropName>k__BackingField will be generated. There is no reason to consider them in comparison if CompareProperties=true - in that case both the value from PropName.get (which returns the backing field) and the backing field will be compared. Thanks to this trick you can remove the number of comparisons in half if the code consists of auto-properties with a small number of declared private fields. That is, ComparePrivateFields=true + ComparePrivateProperties=true will typically be about half as slow as ComparePrivateFields=true + ComparePrivateProperties=true + CompareBackingFields=false.

resolved by #279


Fix test failure in lax_control_flow_test on Mac ARM.

Fixes https://github.com/google/jax/issues/14793 (the other issues in that bug no longer reproduce).
https://github.com/jax-ml/ml_dtypes/pull/112 is needed to fix some spurious cast warnings.

It looks like the only operative difference here is a looser atol in the else: clause, yes? I was initially confused by this block of definitions being moved.

Yes, that's unrelated. I moved the block because I think there's a latent bug in this test harness: scan sometimes gets jit-transformed in the lines above.


Add swap utility and update string reverse method

This is my very first try to add to something an opensource project, and something very simple. I hope If did something wrong, I will get a feedback to learn something. Thanks.

Just add header guards to "utility.hpp" and I will merge it (use ifndef/define/endif and not pragma).

Just add header guards to "utility.hpp" and I will merge it (use ifndef/define/endif and not pragma).

Added.

Added.


Failed to read correct length, returned 0

Describe the bug
RPIBOOT: build-date Feb  9 2024 version 20221215~105525 20a431c6
Waiting for BCM2835/6/7/2711/2712...
Loading embedded: bootcode4.bin
Sending bootcode.bin
Failed to read correct length, returned 0
chhe@pop-os:~/usbboot$ sudo ./rpiboot -d msd
RPIBOOT: build-date Feb  9 2024 version 20221215~105525 20a431c6
Loading: msd/bootcode.bin
Loading: msd/bootcode4.bin
Waiting for BCM2835/6/7/2711/2712...
Loading: msd/bootcode4.bin
Sending bootcode.bin
Failed to read correct length, returned 0
chhe@pop-os:~/usbboot$ sudo ./rpiboot -d recovery
RPIBOOT: build-date Feb  9 2024 version 20221215~105525 20a431c6
Loading: recovery/bootcode4.bin
Waiting for BCM2835/6/7/2711/2712...
Loading: recovery/bootcode4.bin
Sending bootcode.bin
Failed to read correct length, returned 0
Steps to reproduce the behaviour
plugged in new cm4 with waveshare baseboard b
tried it with 2 new units
chhe@pop-os:~/usbboot$ sudo ./rpiboot
RPIBOOT: build-date Feb  9 2024 version 20221215~105525 20a431c6
Waiting for BCM2835/6/7/2711/2712...
Loading embedded: bootcode4.bin
Sending bootcode.bin
Failed to read correct length, returned 0
chhe@pop-os:~/usbboot$ sudo ./rpiboot -d msd
RPIBOOT: build-date Feb  9 2024 version 20221215~105525 20a431c6
Loading: msd/bootcode.bin
Loading: msd/bootcode4.bin
Waiting for BCM2835/6/7/2711/2712...
Loading: msd/bootcode4.bin
Sending bootcode.bin
Failed to read correct length, returned 0
chhe@pop-os:~/usbboot$ sudo ./rpiboot -d recovery
RPIBOOT: build-date Feb  9 2024 version 20221215~105525 20a431c6
Loading: recovery/bootcode4.bin
Waiting for BCM2835/6/7/2711/2712...
Loading: recovery/bootcode4.bin
Sending bootcode.bin
Failed to read correct length, returned 0
Device(s)
Raspberry Pi CM4
Compute Module IO board.
Waveshare B<se Board B
RPIBOOT logs
No response
Kernel logs
[4565296.966249] usb 1-6.7.2: New USB device found, idVendor=0a5c, idProduct=2711, bcdDevice= 0.00
[4565296.966257] usb 1-6.7.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[4565296.966260] usb 1-6.7.2: Product: BCM2711 Boot
[4565296.966263] usb 1-6.7.2: Manufacturer: Broadcom
[4565296.966266] usb 1-6.7.2: SerialNumber: f784ddd8
[4565492.086412] usb 1-6.7.2: USB disconnect, device number 119
[4567716.518542] usb 1-6.7.2: new full-speed USB device number 120 using xhci_hcd
[4567716.727869] usb 1-6.7.2: config index 0 descriptor too short (expected 55, got 32)
[4567716.727878] usb 1-6.7.2: config 1 interface 0 altsetting 0 endpoint 0x1 has invalid maxpacket 512, setting to 64
[4567716.727882] usb 1-6.7.2: config 1 interface 0 altsetting 0 endpoint 0x2 has invalid maxpacket 512, setting to 64
[4567716.743847] usb 1-6.7.2: New USB device found, idVendor=0a5c, idProduct=2711, bcdDevice= 0.00
[4567716.743852] usb 1-6.7.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[4567716.743855] usb 1-6.7.2: Product: BCM2711 Boot
[4567716.743857] usb 1-6.7.2: Manufacturer: Broadcom
[4567716.743860] usb 1-6.7.2: SerialNumber: f784ddd8
Device UART logs
No response

This sounds like a hardware issue with the USB cable / WaveShare board assuming that the host computer is an RPi
Please check the troubleshooting guide
https://github.com/raspberrypi/usbboot?tab=readme-ov-file#troubleshooting

Closed due to inactivity


Update companies with EPAM

WFH encouraged from today, travel, visitors, event restrictions were already in place
Adds or updates the following companies, events, or universities:

Checklist
Company updates

[x] I have put the most recent relevant date in the "Last Update" column
[ ] I have linked to the article about the change, not the company's homepage (Please put N/A if there is no public post)

Event updates

[ ] I have linked to the article about the change, not the event's homepage

University updates

[ ] I have linked to the article about the change, not the university's homepage

Closing due to rebase and staleness. Feel free to re-open after fixes, thanks for your patience.


Install oh-my-zsh as part of the ansible playbook

Since oh-my-zsh is a prerequisite to things working it should be brought in to the playbook and deployed there.

Completed in commit bda9f14df5a2c67590c259549bc324a111b4512b


Firebase Storage: List files

Hi,
the List Files API seems to be completely missing in the Unity SDK.
Without the ability to list files the storage API is not useful. When will this be added?

Yup, I've been looking everywhere as well but can't find it. 😞

Doesn't appear to be implemented, which is a shame because the underlying iOS/Android SDKs do support it. Does anyone know the official channel to file a feature request?

I'm also looking forward to have this feature

There's a bunch of rest apis you could use but won't be as good as the grpc native versions

For management purpose, let me use https://github.com/firebase/firebase-unity-sdk/issues/98 as the main feature request post since it is the oldest (and the age of the FR matters :))
Please upvote that post if you consider it important to your team.
Thank you!


Module 4 exercises [Kesego Motswasele]

Please "drag & drop" exercise 1 excel file below.

MODULE 4 exercise 1and 2.xlsx

Please "drag & drop" exercise 2 excel file below.

Please "drag & drop" exercise 3 pdf file below.

Please UPDATE THE TITLE of this "Issue" in the title bar above with your name.

If you haven't done so, please go back to Module 4 and make sure to take
the post-training survey. Participating in surveys is required for receiving
the "GALUP Certificate" by the University of Florida.

Hi Kesego, your exercise 1 is correct. However, since we only have four farmers each of them should get a weight of 0.25 (instead of 0.2) in the final decision. Please update your exercise and resubmit.

Good day.
kindly find the updated exercise 2 module 4 resubmission.
Thank you.
On Wed, Nov 29, 2023 at 1:48 PM Changjie Chen @.***>
wrote:

Hi Kesego, your exercise 1 is correct. However, since we only have four
farmers each of them should get a weight of 0.25 (instead of 0.2) in the
final decision. Please update your exercise and resubmit.
—
Reply to this email directly, view it on GitHub
https://github.com/SERVIR-WA/GALUP/issues/648#issuecomment-1831744768,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BD32P6BRS5IYE2WDSWZGRM3YG4OJZAVCNFSM6AAAAAA73CNJFWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZRG42DINZWHA
.
You are receiving this because you authored the thread.Message ID:
@.***>

Hello Kesego, can you please submit your exercise properly from the module link, not by replying to your email. GitHub cannot read files you attached to your email. Thanks


imsakparameter exception

Getting this error trying to run your example.
Exception has occurred.
Tried to build class "PrayerCalculationSettings" but nested builder for field "imsakParameter" threw: Tried to construct class "PrayerCalculationParameter" with null field "type". This is forbidden; to allow it, mark "type" with @nullable.

Sorry for the late reply @fawadkhanucp. Will investigate.

np. im using version 0.0.2 in the meantime and it's working perfectly.

Sorry for the late reply @fawadkhanucp. Will investigate.

I have the exact same problem
Launching lib/main.dart on iPhone XR in debug mode... Starting Xcode build... Xcode build done. Syncing files to device iPhone XR... flutter: ══╡ EXCEPTION CAUGHT BY WIDGETS LIBRARY ╞═══════════════════════════════════════════════════════════ flutter: The following BuiltValueNestedFieldError was thrown building Builder: flutter: Tried to build class "PrayerCalculationSettings" but nested builder for field "imsakParameter" flutter: threw: Tried to construct class "PrayerCalculationParameter" with null field "type".  This is forbidden; to allow it, mark "type" with @nullable. flutter: Another exception was thrown: Tried to build class "PrayerCalculationSettings" but nested builder for field "imsakParameter" threw: Tried to construct class "PrayerCalculationParameter" with null field "type". This is forbidden; to allow it, mark "type" with @nullable.

is this updated ..?

I got same issue in flutter
flutter: ══╡ EXCEPTION CAUGHT BY WIDGETS LIBRARY ╞═══════════════════════════════════════════════════════════
flutter: The following BuiltValueNestedFieldError was thrown building Builder:
flutter: Tried to build class "PrayerCalculationSettings" but nested builder for field "imsakParameter"
flutter: threw: Tried to construct class "PrayerCalculationParameter" with null field "type".  This is
flutter: forbidden; to allow it, mark "type" with @nullable.
flutter:
flutter: When the exception was thrown, this was the stack:
flutter: #0      PrayerCalculationSettingsBuilder.build (package:libpray/src/models/prayer_calculation_settings.g.dart:430:9)
flutter: #1      new _$PrayerCalculationSettings (package:libpray/src/models/prayer_calculation_settings.g.dart:175:65)
flutter: #2      new _MyHomePageState (package:flutter_prayer_time/main.dart:40:46)
flutter: #3      MyHomePage.createState (package:flutter_prayer_time/main.dart:27:37)
flutter: #4      new StatefulElement (package:flutter/src/widgets/framework.dart:3989:25)
flutter: #5      StatefulWidget.createElement (package:flutter/src/widgets/framework.dart:802:38)
flutter: #6      Element.inflateWidget (package:flutter/src/widgets/framework.dart:3082:40)
flutter: #7      Element.updateChild (package:flutter/src/widgets/framework.dart:2887:12)
flutter: #8      SingleChildRenderObjectElement.mount (package:flutter/src/widgets/framework.dart:5092:14)
flutter: #9      Element.inflateWidget (package:flutter/src/widgets/framework.dart:3084:14)
flutter: #10     Element.updateChild (package:flutter/src/widgets/framework.dart:2887:12)
flutter: #11     ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:3935:16)
flutter: #12     Element.rebuild (package:flutter/src/widgets/framework.dart:3721:5)
flutter: #13     StatelessElement.update (package:flutter/src/widgets/framework.dart:3981:5)
flutter: #14     Element.updateChild (package:flutter/src/widgets/framework.dart:2876:15)
flutter: #15     SingleChildRenderObjectElement.update (package:flutter/src/widgets/framework.dart:5099:14)
flutter: #16     Element.updateChild (package:flutter/src/widgets/framework.dart:2876:15)
flutter: #17     SingleChildRenderObjectElement.update (package:flutter/src/widgets/framework.dart:5099:14)
flutter: #18     Element.updateChild (package:flutter/src/widgets/framework.dart:2876:15)
flutter: #19     RenderObjectElement.updateChildren (package:flutter/src/widgets/framework.dart:4817:32)
flutter: #20     MultiChildRenderObjectElement.update (package:flutter/src/widgets/framework.dart:5208:17)
flutter: #21     Element.updateChild (package:flutter/src/widgets/framework.dart:2876:15)
flutter: #22     ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:3935:16)
flutter: #23     Element.rebuild (package:flutter/src/widgets/framework.dart:3721:5)
flutter: #24     StatefulElement.update (package:flutter/src/widgets/framework.dart:4085:5)
flutter: #25     Element.updateChild (package:flutter/src/widgets/framework.dart:2876:15)
flutter: #26     SingleChildRenderObjectElement.update (package:flutter/src/widgets/framework.dart:5099:14)
flutter: #27     Element.updateChild (package:flutter/src/widgets/framework.dart:2876:15)
flutter: #28     ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:3935:16)
flutter: #29     Element.rebuild (package:flutter/src/widgets/framework.dart:3721:5)
flutter: #30     StatefulElement.update (package:flutter/src/widgets/framework.dart:4085:5)
flutter: #31     Element.updateChild (package:flutter/src/widgets/framework.dart:2876:15)
flutter: #32     SingleChildRenderObjectElement.update (package:flutter/src/widgets/framework.dart:5099:14)
flutter: #33     Element.updateChild (package:flutter/src/widgets/framework.dart:2876:15)
flutter: #34     ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:3935:16)
flutter: #35     Element.rebuild (package:flutter/src/widgets/framework.dart:3721:5)
flutter: #36     StatefulElement.update (package:flutter/src/widgets/framework.dart:4085:5)
flutter: #37     Element.updateChild (package:flutter/src/widgets/framework.dart:2876:15)
flutter: #38     SingleChildRenderObjectElement.update (package:flutter/src/widgets/framework.dart:5099:14)
flutter: #39     Element.updateChild (package:flutter/src/widgets/framework.dart:2876:15)
flutter: #40     ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:3935:16)
flutter: #41     Element.rebuild (package:flutter/src/widgets/framework.dart:3721:5)
flutter: #42     StatefulElement.update (package:flutter/src/widgets/framework.dart:4085:5)
flutter: #43     Element.updateChild (package:flutter/src/widgets/framework.dart:2876:15)
flutter: #44     ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:3935:16)
flutter: #45     Element.rebuild (package:flutter/src/widgets/framework.dart:3721:5)
flutter: #46     StatelessElement.update (package:flutter/src/widgets/framework.dart:3981:5)
flutter: #47     Element.updateChild (package:flutter/src/widgets/framework.dart:2876:15)
flutter: #48     ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:3935:16)
flutter: #49     Element.rebuild (package:flutter/src/widgets/framework.dart:3721:5)
flutter: #50     StatefulElement.update (package:flutter/src/widgets/framework.dart:4085:5)
flutter: #51     Element.updateChild (package:flutter/src/widgets/framework.dart:2876:15)
flutter: #52     SingleChildRenderObjectElement.update (package:flutter/src/widgets/framework.dart:5099:14)
flutter: #53     Element.updateChild (package:flutter/src/widgets/framework.dart:2876:15)
flutter: #54     ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:3935:16)
flutter: #55     Element.rebuild (package:flutter/src/widgets/framework.dart:3721:5)
flutter: #56     ProxyElement.update (package:flutter/src/widgets/framework.dart:4219:5)
flutter: #57     _InheritedNotifierElement.update (package:flutter/src/widgets/inherited_notifier.dart:94:11)
flutter: #58     Element.updateChild (package:flutter/src/widgets/framework.dart:2876:15)
flutter: #59     SingleChildRenderObjectElement.update (package:flutter/src/widgets/framework.dart:5099:14)
flutter: #60     Element.updateChild (package:flutter/src/widgets/framework.dart:2876:15)
flutter: #61     ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:3935:16)
flutter: #62     Element.rebuild (package:flutter/src/widgets/framework.dart:3721:5)
flutter: #63     StatefulElement.update (package:flutter/src/widgets/framework.dart:4085:5)
flutter: #64     Element.updateChild (package:flutter/src/widgets/framework.dart:2876:15)
flutter: #65     ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:3935:16)
flutter: #66     Element.rebuild (package:flutter/src/widgets/framework.dart:3721:5)
flutter: #67     StatelessElement.update (package:flutter/src/widgets/framework.dart:3981:5)
flutter: #68     Element.updateChild (package:flutter/src/widgets/framework.dart:2876:15)
flutter: #69     SingleChildRenderObjectElement.update (package:flutter/src/widgets/framework.dart:5099:14)
flutter: #70     Element.updateChild (package:flutter/src/widgets/framework.dart:2876:15)
flutter: #71     ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:3935:16)
flutter: #72     Element.rebuild (package:flutter/src/widgets/framework.dart:3721:5)
flutter: #73     ProxyElement.update (package:flutter/src/widgets/framework.dart:4219:5)
flutter: #74     Element.updateChild (package:flutter/src/widgets/framework.dart:2876:15)
flutter: #75     ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:3935:16)
flutter: #76     Element.rebuild (package:flutter/src/widgets/framework.dart:3721:5)
flutter: #77     BuildOwner.buildScope (package:flutter/src/widgets/framework.dart:2340:33)
flutter: #78     _WidgetsFlutterBinding&BindingBase&GestureBinding&ServicesBinding&SchedulerBinding&PaintingBinding&SemanticsBinding&RendererBinding&WidgetsBinding.drawFrame (package:flutter/src/widgets/binding.dart:700:20)
flutter: #79     _WidgetsFlutterBinding&BindingBase&GestureBinding&ServicesBinding&SchedulerBinding&PaintingBinding&SemanticsBinding&RendererBinding._handlePersistentFrameCallback (package:flutter/src/rendering/binding.dart:285:5)
flutter: #80     _WidgetsFlutterBinding&BindingBase&GestureBinding&ServicesBinding&SchedulerBinding._invokeFrameCallback (package:flutter/src/scheduler/binding.dart:1016:15)
flutter: #81     _WidgetsFlutterBinding&BindingBase&GestureBinding&ServicesBinding&SchedulerBinding.handleDrawFrame (package:flutter/src/scheduler/binding.dart:958:9)
flutter: #82     _WidgetsFlutterBinding&BindingBase&GestureBinding&ServicesBinding&SchedulerBinding.scheduleWarmUpFrame. (package:flutter/src/scheduler/binding.dart:784:7)
flutter: #84     _Timer._runTimers (dart:isolate-patch/timer_impl.dart:382:19)
flutter: #85     _Timer._handleMessage (dart:isolate-patch/timer_impl.dart:416:5)
flutter: #86     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:172:12)
flutter: (elided one frame from package dart:async-patch)
flutter: ════════════════════════════════════════════════════════════════════════════════════════════════════

The same error here with Flutter, any help @zulfahmi93

It's been long time no update on this issue.

Try below:
PrayerCalculationSettings settings = PrayerCalculationSettings((PrayerCalculationSettingsBuilder b) =>
b
..calculationMethod.replace(CalculationMethod.fromPreset(preset: CalculationMethodPreset.departmentOfIslamicAdvancementOfMalaysia))
..imsakParameter.replace(PrayerCalculationParameter((PrayerCalculationParameterBuilder c) => c..value = 0 ..type = PrayerCalculationParameterType.minutesAdjust))
..juristicMethod.replace(JuristicMethod((JuristicMethodBuilder e) => e..preset = JuristicMethodPreset.hanafi ..timeOfShadow = 2))
..highLatitudeAdjustment = HighLatitudeAdjustment.angleBased
..imsakMinutesAdjustment = 0
..fajrMinutesAdjustment = 0
..sunriseMinutesAdjustment = 0
..dhuhaMinutesAdjustment = 0
..dhuhrMinutesAdjustment = 0
..asrMinutesAdjustment = 0
..maghribMinutesAdjustment = 0
..ishaMinutesAdjustment = 0
);

@mamedshahmaliyev thanks, working.

Try below:
PrayerCalculationSettings settings = PrayerCalculationSettings((PrayerCalculationSettingsBuilder b) =>
b
..calculationMethod.replace(CalculationMethod.fromPreset(preset: CalculationMethodPreset.departmentOfIslamicAdvancementOfMalaysia))
..imsakParameter.replace(PrayerCalculationParameter((PrayerCalculationParameterBuilder c) => c..value = 0 ..type = PrayerCalculationParameterType.minutesAdjust))
..juristicMethod.replace(JuristicMethod((JuristicMethodBuilder e) => e..preset = JuristicMethodPreset.hanafi ..timeOfShadow = 2))
..highLatitudeAdjustment = HighLatitudeAdjustment.angleBased
..imsakMinutesAdjustment = 0
..fajrMinutesAdjustment = 0
..sunriseMinutesAdjustment = 0
..dhuhaMinutesAdjustment = 0
..dhuhrMinutesAdjustment = 0
..asrMinutesAdjustment = 0
..maghribMinutesAdjustment = 0
..ishaMinutesAdjustment = 0
);

Working BUT it displays wrong time for IMSAK. Showing syuruk time instead. Any fix for this? Where can I adjust? Thanks


Create Valkey Integration

Problem Statement
Valkey is an open-source fork of Redis. We have an integration for Redis, but not for Valkey yet.
Solution Brainstorm
Consider creating an integration for Valkey with the same features as our Redis integration.

It would be wonderful, especially since api is the same.


Dynamic params for folder

Hello! Please add dynamic params for folder.
├── app.ts
├── routes
    ├── index.ts
    ├── :posts // dynamic params
        ├── index.ts
        └── :id.ts
    └── users.ts
└── package.json

Thanks!

hey @Rysakov1986, isn't this supported already? If not, feel free to reopen the issue. Maybe there's a note missing in the docs? What do you think?

I think I can answer this question when you add Windows support))


fix(ui): ensure settings menu shows on top

Description:
Ensure that we import styles/variables.scss before attempting to use the z() helper function that it provides.
Motivation and Context:
Several of our elements were missing z-index property, causing them to display incorrectly in the app.
How Has This Been Tested?
Manually verify z-index ordering is correct throughout the app.
Screenshots (if appropriate):
Before:

After:

Types of changes:
Bug fix
Checklist:

[x] My code follows the code style of this project.
[x] I have reviewed and updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes where needed.
[ ] All new and existing tests passed.
[x] My commits have been squashed into a concise set of changes.

Coverage remained the same at 16.344% when pulling<PHONE_NUMBER>61fbe013431d022314da1959987c50 on mrfelton:fix/settings-menu-zindex into 19c1c85a6ba848dfb69cf2e930194dbf257a9318 on LN-Zap:master.

Tested ACK 8325385


Release version 0.2.0

Can we do a release of 0.2.0-SNAPSHOT to access GA4GH schemas when https://github.com/bigdatagenomics/bdg-convert/pull/35 is merged? This is for use in https://github.com/bigdatagenomics/mango/pull/316

+1

Fixed in commit f58b3451a561f579e272d2727b3a0f6651768ca4


receptor terms incorrectly under 'receptor signaling protein activity'

As just discussed in the office, these receptor terms shouldn't be under 'receptor signaling protein activity ; GO:0005057' :
ethylene receptor activity ; GO:0038199
neurotransmitter receptor activity involved in regulation of postsynaptic cytosolic calcium levels ; GO:0099583
neurotransmitter receptor activity involved in regulation of presynaptic cytosolic calcium levels ; GO:0099582
@dosumis is going to trace the inferences- probably stems back to cytosolic calcium signaling/homeostasis terms.

We need an OBA term for cytosolic calcium ion concentration - rather than using 'occurs in'.  In fact, we already have an OBA tissue for this: https://github.com/obophenotype/bio-attribute-ontology/issues/10

Second (more general problem)  comes from part relationship of activity to sig pathway, which is defined as intracellular

@rebeccafoulger - Any suggestion for how to fix this?

‘receptor signaling protein activity’ Equivalent to ‘signal transducer activity’ and (‘occurs in’ some intracellular) is too broad.
Need something along lines of:
preceded_by: signaling receptor activity
or
causally_downstream_of: signaling receptor activity
or
regulated_by: signaling receptor activity (can be direct or indirect)
any of those suitable for MF classification?
NB: Note to myself to remove 'receptor agonist activity ; GO:0048018' from under 'signal transducer activity'- shouldn't be there.

‘receptor signaling protein activity’ Equivalent to ‘signal transducer activity’ and (‘occurs in’ some intracellular) is too broad.

OK.  Can see that now - has to encompass things downstream of intracellular receptors.
'regulated by' makes sense to me, but we don't currently have any axiomatisation to support it: would require extensive addition of regulates/directly regulates relationships in this branch.  If we change, we'll need to comb through inferred subclasses and either assert or axiomatise.

Thinking about this some more, we can only crudely axiomatise.  For cases where a signal transducer is downstream of different receptors under different circumstances (perhaps we should never assume otherwise?) we can only use the most general axiom 'regulated by' some 'signaling receptor activity' - not specifying which.

Fixed the inference through reg cytosolic Ca2+ concentration by switching to OBA-based logical def.

Have deleted logical def:
‘receptor signaling protein activity’ Equivalent to ‘signal transducer activity’ and (‘occurs in’ some intracellular)

cleaned up classification underneath

Holding off on adding replacement logical def.
@cmungall  - any opinion on using:
EquivalentTo: molecular_function
that (regulated_by some 'signaling receptor activity')
and (part_of some 'signal transduction')
Not entirely confident of quantification on regulated_by in this case.


Revert "test coverage lib/debug"

Reverts OpenZWave/Zwave2Mqtt#390

@Tomasz69 Has it broke something? Everything was working on my tests

@chrisns Do you know?

@robertsLando no, i'd resisted responding with a "works for me" :)

Let's see it @Tomasz69 tell us what it has break

@chrisns I suggest to open a new PR with that fix in the review, just add that line


[BUG] Organization update doesn't handle case where partner would have no request type set gracefully

Summary
If an organization disallows a request type, and a partner only has that request type,  the user will get a nasty error (i.e a 500 error)  This should be handled gracefully with a friendly error message, naming the partner affected.
Why fix
It is,  I will grant you, a rare case, but a bank should be able to be notified gracefully of the problem.
Details
If a bank tries to update their org, and their change would result in a partner not having any request capability,  please display an error "Please update [partner name] so that they could make requests if you completed this change, then try again.  Thank you."
Notes
There is an organization update service that seems to be checking if the organizations can make requests,  but doesn't throw an error if they don't.   That is related, but probably not the actual issue here.
Criteria for completion

[ ] System handles the case where a partner would be left with no request capability gracefully as described above
[ ] Tests to demonstrate this.

Hi there! I'd like to make an attempt at tackling this, please!

Go for it!

Just noting that I took a few days to get acquainted with the Repo before starting this ticket as it's my first!  But I am getting pretty close and should have a PR soon :)

Hopping off this one for now... working through interviews that have been taking up my time lately!

I accidentally removed my assignment on this instead of a different one I was on!  I am still plugging away at this and will hopefully have a final PR in tomorrow. Working with @dorner to work out a few kinks w/ CI.

Thank you for your contribution! This is going out to the production humanessentials.app now!


numba: init at 0.20.0

This is an attempt at packaging numba, a Python JIT using LLVM.
Unfortunately llvmlite, the bindings, seem to segfault.

Disabling static linking of libstdc++ did the track.

Travis successfully built packages for Python 2.7, 3.3 and 3.4.

@teh @domenkozar @garbas
Can this be merged as it is now?

I don't have merge permissions but I did test this and it works.

tested locally as well. will merge in a second!


Let community pin locations, store in gsheets, render as layer

Closes #34
Video shows how community can add pins to a location via google forms and then we use gsheets to render the points as a layer. @planemad thoughts?

enable edit pin mode (bottom right)
click on map, shows tooltip
click on link to forms, with pre-populated lat,long
enter details, submit form
back on amche site, select community pins layer
click on red circles to view location pin details

https://github.com/user-attachments/assets/a450ec77-c7d3-4d16-834b-846c87197b6b

OMG @pratapvardhan this is fantastic!

@planemad added

Capture layer ids in form, but won't show on popup
Display the note comment field
Display when the note was added in the popup.

Here's the spreadsheet: https://docs.google.com/spreadsheets/d/1Y0l4aSIdks8G3lmxSxSKxuzLoARL-FCiYbTL9a0b3O0/edit?resourcekey=&gid=485622101#gid=485622101
We don't collect email as of now, so public spreadsheet (view-only) should work?

How about we also enable the pin layer to view existing pins when we click the pin button. Existing pins are useful context when adding any new pin.

And I'm liking the pin/notes language with the design of the feature 💯