Several important RegistryCI updates

This pull request makes the following changes:
Major changes:

Update the version of RegistryCI to 0.4.0 (latest version).
Update the julia-actions/setup-julia action to 1.0.1 (latest version).
Run the AutoMerge schedule/cron job five times per hour. Each cron job only takes 2-3 minutes to complete, so I think that it is very reasonable to run it five times per hour. Honestly, we could run it ten times per hour, but I picked the more conservative five times.
Add jlbuild as an authorized AutoMerge user. The list of authorized AutoMerge users is now: authorized_authors=["JuliaRegistrator", "jlbuild"]

Minor changes:

Rename the AutoMerge job from the generic build to AutoMerge.
Add a more descriptive name for the Install dependencies step.

Please note that the waiting periods have not been modified, i.e. new packages remains unchanged at Day(3) and new versions remains unchanged at Minute(15). This means that a new package PR will never be merged if it is less than three days old, and a new version PR will never be merged if it is less than 15 minutes old.

The RegistryCI integration tests pass on 0.4.0, so in theory this PR should be safe.


Insane experiment to optimize sum

Continuing from https://github.com/prometheus/prometheus/pull/8602

commits in order, earliest to latest
before.txt: f1a3dbb (prometheus:main)
after_orig.txt: f374523 Experiment to optimize most common aggregations + Update from rebase
after_todo.txt: 88e4b1d Simplify the code to expect only 1 expr + Work on more TODOs
after_keys.txt: 8b67c5e Process series in order of grouping keys
after_ag.txt: 52acad2 Add more simple aggregations
comparisons
compare_ag.txt: before.txt -> after_ag.txt (great improvement overall)
compare_orig_todo.txt: after_orig.txt -> after_todo.txt (about the same)
compare_orig_ag.txt: after_orig.txt -> after_ag.txt (a bit worse)
compare_todo_keys.txt: after_todo.txt -> after_keys.txt (a bit worse)
compare_todo_ag.txt: after_todo.txt -> after_ag.txt (a bit worse)
compare_keys_ag.txt: after_keys.txt -> after_ag.txt (a bit worse)
summary
working on the TODOs in 88e4b1d didn't make performance worse, and it's necessary, so it's good to keep
processing series in order of grouping keys in 8b67c5e is a failed attempt at optimisation, so reverted
adding more aggregations in 52acad2 has minor impact on performance but it's useful functionality, so it's good to keep

Looking at this during the bug scrub.
Since this draft has been sitting untouched for a year, we'll close this now. @zenador this should not discourage you from further work. We would just like to clean out the backlog of PRs.


the adapter is not able to connect to hoover/hOn Server anymore

Describe the bug
since some days ago I get this Message into my log files "Message":"User is not authorized to access this resource with an explicit deny" and the adapter could not connect to the server anymore.
Screenshots & Logfiles
2023-06-04 00:06:53.455 - error: hoover.0 (1248) https://api-iot.he.services/commands/v1/context?macAddress=10-97-bd-01-b6-30&applianceType=WM&category=CYCLE
2023-06-04 00:06:53.455 - error: hoover.0 (1248) AxiosError: Request failed with status code 403
2023-06-04 00:06:53.455 - error: hoover.0 (1248) {"Message":"User is not authorized to access this resource with an explicit deny"}
2023-06-04 00:16:53.344 - error: hoover.0 (1248) https://api-iot.he.services/commands/v1/context?macAddress=10-97-bd-01-b6-30&applianceType=WM&category=CYCLE
2023-06-04 00:16:53.344 - error: hoover.0 (1248) AxiosError: Request failed with status code 403
2023-06-04 00:16:53.344 - error: hoover.0 (1248) {"Message":"User is not authorized to access this resource with an explicit deny"}
2023-06-04 00:26:53.315 - error: hoover.0 (1248) https://api-iot.he.services/commands/v1/context?macAddress=10-97-bd-01-b6-30&applianceType=WM&category=CYCLE
2023-06-04 00:26:53.315 - error: hoover.0 (1248) AxiosError: Request failed with status code 403
2023-06-04 00:26:53.315 - error: hoover.0 (1248) {"Message":"User is not authorized to access this resource with an explicit deny"}
2023-06-04 00:36:53.362 - error: hoover.0 (1248) https://api-iot.he.services/commands/v1/context?macAddress=10-97-bd-01-b6-30&applianceType=WM&category=CYCLE
2023-06-04 00:36:53.363 - error: hoover.0 (1248) AxiosError: Request failed with status code 403
2023-06-04 00:36:53.363 - error: hoover.0 (1248) {"Message":"User is not authorized to access this resource with an explicit deny"}
2023-06-04 00:46:53.330 - error: hoover.0 (1248) https://api-iot.he.services/commands/v1/context?macAddress=10-97-bd-01-b6-30&applianceType=WM&category=CYCLE
2023-06-04 00:46:53.330 - error: hoover.0 (1248) AxiosError: Request failed with status code 403
2023-06-04 00:46:53.330 - error: hoover.0 (1248) {"Message":"User is not authorized to access this resource with an explicit deny"}
2023-06-04 00:56:53.339 - error: hoover.0 (1248) https://api-iot.he.services/commands/v1/context?macAddress=10-97-bd-01-b6-30&applianceType=WM&category=CYCLE
2023-06-04 00:56:53.340 - error: hoover.0 (1248) AxiosError: Request failed with status code 403
2023-06-04 00:56:53.340 - error: hoover.0 (1248) {"Message":"User is not authorized to access this resource with an explicit deny"}
2023-06-04 01:06:53.396 - error: hoover.0 (1248) https://api-iot.he.services/commands/v1/context?macAddress=10-97-bd-01-b6-30&applianceType=WM&category=CYCLE
2023-06-04 01:06:53.396 - error: hoover.0 (1248) AxiosError: Request failed with status code 403
2023-06-04 01:06:53.396 - error: hoover.0 (1248) {"Message":"User is not authorized to access this resource with an explicit deny"}
2023-06-04 01:16:53.343 - error: hoover.0 (1248) https://api-iot.he.services/commands/v1/context?macAddress=10-97-bd-01-b6-30&applianceType=WM&category=CYCLE
2023-06-04 01:16:53.343 - error: hoover.0 (1248) AxiosError: Request failed with status code 403
2023-06-04 01:16:53.343 - error: hoover.0 (1248) {"Message":"User is not authorized to access this resource with an explicit deny"}
2023-06-04 01:26:53.340 - error: hoover.0 (1248) https://api-iot.he.services/commands/v1/context?macAddress=10-97-bd-01-b6-30&applianceType=WM&category=CYCLE
2023-06-04 01:26:53.340 - error: hoover.0 (1248) AxiosError: Request failed with status code 403
2023-06-04 01:26:53.340 - error: hoover.0 (1248) {"Message":"User is not authorized to access this resource with an explicit deny"}
2023-06-04 01:36:53.313 - error: hoover.0 (1248) https://api-iot.he.services/commands/v1/context?macAddress=10-97-bd-01-b6-30&applianceType=WM&category=CYCLE
2023-06-04 01:36:53.314 - error: hoover.0 (1248) AxiosError: Request failed with status code 403
2023-06-04 01:36:53.314 - error: hoover.0 (1248) {"Message":"User is not authorized to access this resource with an explicit deny"}
2023-06-04 01:46:53.350 - error: hoover.0 (1248) https://api-iot.he.services/commands/v1/context?macAddress=10-97-bd-01-b6-30&applianceType=WM&category=CYCLE
2023-06-04 01:46:53.350 - error: hoover.0 (1248) AxiosError: Request failed with status code 403
2023-06-04 01:46:53.350 - error: hoover.0 (1248) {"Message":"User is not authorized to access this resource with an explicit deny"}
2023-06-04 01:56:53.332 - error: hoover.0 (1248) https://api-iot.he.services/commands/v1/context?macAddress=10-97-bd-01-b6-30&applianceType=WM&category=CYCLE
2023-06-04 01:56:53.332 - error: hoover.0 (1248) AxiosError: Request failed with status code 403
2023-06-04 01:56:53.332 - error: hoover.0 (1248) {"Message":"User is not authorized to access this resource with an explicit deny"}
2023-06-04 02:06:53.345 - error: hoover.0 (1248) https://api-iot.he.services/commands/v1/context?macAddress=10-97-bd-01-b6-30&applianceType=WM&category=CYCLE
2023-06-04 02:06:53.345 - error: hoover.0 (1248) AxiosError: Request failed with status code 403
2023-06-04 02:06:53.345 - error: hoover.0 (1248) {"Message":"User is not authorized to access this resource with an explicit deny"}
2023-06-04 02:16:53.380 - error: hoover.0 (1248) https://api-iot.he.services/commands/v1/context?macAddress=10-97-bd-01-b6-30&applianceType=WM&category=CYCLE
2023-06-04 02:16:53.380 - error: hoover.0 (1248) AxiosError: Request failed with status code 403
2023-06-04 02:16:53.380 - error: hoover.0 (1248) {"Message":"User is not authorized to access this resource with an explicit deny"}
2023-06-04 02:26:53.347 - error: hoover.0 (1248) https://api-iot.he.services/commands/v1/context?macAddress=10-97-bd-01-b6-30&applianceType=WM&category=CYCLE
2023-06-04 02:26:53.347 - error: hoover.0 (1248) AxiosError: Request failed with status code 403
2023-06-04 02:26:53.347 - error: hoover.0 (1248) {"Message":"User is not authorized to access this resource with an explicit deny"}
2023-06-04 02:36:53.377 - error: hoover.0 (1248) https://api-iot.he.services/commands/v1/context?macAddress=10-97-bd-01-b6-30&applianceType=WM&category=CYCLE
2023-06-04 02:36:53.377 - error: hoover.0 (1248) AxiosError: Request failed with status code 403
2023-06-04 02:36:53.377 - error: hoover.0 (1248) {"Message":"User is not authorized to access this resource with an explicit deny"}
2023-06-04 02:46:53.353 - error: hoover.0 (1248) https://api-iot.he.services/commands/v1/context?macAddress=10-97-bd-01-b6-30&applianceType=WM&category=CYCLE
2023-06-04 02:46:53.353 - error: hoover.0 (1248) AxiosError: Request failed with status code 403
2023-06-04 02:46:53.353 - error: hoover.0 (1248) {"Message":"User is not authorized to access this resource with an explicit deny"}
2023-06-04 02:56:53.330 - error: hoover.0 (1248) https://api-iot.he.services/commands/v1/context?macAddress=10-97-bd-01-b6-30&applianceType=WM&category=CYCLE
2023-06-04 02:56:53.330 - error: hoover.0 (1248) AxiosError: Request failed with status code 403
2023-06-04 02:56:53.330 - error: hoover.0 (1248) {"Message":"User is not authorized to access this resource with an explicit deny"}
2023-06-04 03:06:53.319 - error: hoover.0 (1248) https://api-iot.he.services/commands/v1/context?macAddress=10-97-bd-01-b6-30&applianceType=WM&category=CYCLE
2023-06-04 03:06:53.319 - error: hoover.0 (1248) AxiosError: Request failed with status code 403
2023-06-04 03:06:53.319 - error: hoover.0 (1248) {"Message":"User is not authorized to access this resource with an explicit deny"}
2023-06-04 03:16:53.335 - error: hoover.0 (1248) https://api-iot.he.services/commands/v1/context?macAddress=10-97-bd-01-b6-30&applianceType=WM&category=CYCLE
2023-06-04 03:16:53.335 - error: hoover.0 (1248) AxiosError: Request failed with status code 403
2023-06-04 03:16:53.335 - error: hoover.0 (1248) {"Message":"User is not authorized to access this resource with an explicit deny"}
2023-06-04 03:26:53.345 - error: hoover.0 (1248) https://api-iot.he.services/commands/v1/context?macAddress=10-97-bd-01-b6-30&applianceType=WM&category=CYCLE
2023-06-04 03:26:53.345 - error: hoover.0 (1248) AxiosError: Request failed with status code 403
2023-06-04 03:26:53.345 - error: hoover.0 (1248) {"Message":"User is not authorized to access this resource with an explicit deny"}
2023-06-04 03:36:53.326 - error: hoover.0 (1248) https://api-iot.he.services/commands/v1/context?macAddress=10-97-bd-01-b6-30&applianceType=WM&category=CYCLE
2023-06-04 03:36:53.326 - error: hoover.0 (1248) AxiosError: Request failed with status code 403
2023-06-04 03:36:53.326 - error: hoover.0 (1248) {"Message":"User is not authorized to access this resource with an explicit deny"}
2023-06-04 03:46:53.351 - error: hoover.0 (1248) https://api-iot.he.services/commands/v1/context?macAddress=10-97-bd-01-b6-30&applianceType=WM&category=CYCLE
2023-06-04 03:46:53.351 - error: hoover.0 (1248) AxiosError: Request failed with status code 403
2023-06-04 03:46:53.351 - error: hoover.0 (1248) {"Message":"User is not authorized to access this resource with an explicit deny"}
2023-06-04 03:56:53.325 - error: hoover.0 (1248) https://api-iot.he.services/commands/v1/context?macAddress=10-97-bd-01-b6-30&applianceType=WM&category=CYCLE
2023-06-04 03:56:53.325 - error: hoover.0 (1248) AxiosError: Request failed with status code 403
2023-06-04 03:56:53.325 - error: hoover.0 (1248) {"Message":"User is not authorized to access this resource with an explicit deny"}
2023-06-04 04:06:53.370 - error: hoover.0 (1248) https://api-iot.he.services/commands/v1/context?macAddress=10-97-bd-01-b6-30&applianceType=WM&category=CYCLE
2023-06-04 04:06:53.371 - error: hoover.0 (1248) AxiosError: Request failed with status code 403
2023-06-04 04:06:53.371 - error: hoover.0 (1248) {"Message":"User is not authorized to access this resource with an explicit deny"}
2023-06-04 04:16:53.327 - error: hoover.0 (1248) https://api-iot.he.services/commands/v1/context?macAddress=10-97-bd-01-b6-30&applianceType=WM&category=CYCLE
2023-06-04 04:16:53.327 - error: hoover.0 (1248) AxiosError: Request failed with status code 403
2023-06-04 04:16:53.327 - error: hoover.0 (1248) {"Message":"User is not authorized to access this resource with an explicit deny"}
2023-06-04 04:26:53.375 - error: hoover.0 (1248) https://api-iot.he.services/commands/v1/context?macAddress=10-97-bd-01-b6-30&applianceType=WM&category=CYCLE
2023-06-04 04:26:53.375 - error: hoover.0 (1248) AxiosError: Request failed with status code 403
2023-06-04 04:26:53.375 - error: hoover.0 (1248) {"Message":"User is not authorized to access this resource with an explicit deny"}
2023-06-04 04:36:53.338 - error: hoover.0 (1248) https://api-iot.he.services/commands/v1/context?macAddress=10-97-bd-01-b6-30&applianceType=WM&category=CYCLE
2023-06-04 04:36:53.338 - error: hoover.0 (1248) AxiosError: Request failed with status code 403
2023-06-04 04:36:53.338 - error: hoover.0 (1248) {"Message":"User is not authorized to access this resource with an explicit deny"}
2023-06-04 04:46:53.546 - error: hoover.0 (1248) https://api-iot.he.services/commands/v1/context?macAddress=10-97-bd-01-b6-30&applianceType=WM&category=CYCLE
2023-06-04 04:46:53.546 - error: hoover.0 (1248) AxiosError: Request failed with status code 403
2023-06-04 04:46:53.547 - error: hoover.0 (1248) {"Message":"User is not authorized to access this resource with an explicit deny"}
2023-06-04 04:56:53.352 - error: hoover.0 (1248) https://api-iot.he.services/commands/v1/context?macAddress=10-97-bd-01-b6-30&applianceType=WM&category=CYCLE
2023-06-04 04:56:53.352 - error: hoover.0 (1248) AxiosError: Request failed with status code 403
2023-06-04 04:56:53.353 - error: hoover.0 (1248) {"Message":"User is not authorized to access this resource with an explicit deny"}
2023-06-04 05:06:53.373 - error: hoover.0 (1248) https://api-iot.he.services/commands/v1/context?macAddress=10-97-bd-01-b6-30&applianceType=WM&category=CYCLE
2023-06-04 05:06:53.374 - error: hoover.0 (1248) AxiosError: Request failed with status code 403
2023-06-04 05:06:53.374 - error: hoover.0 (1248) {"Message":"User is not authorized to access this resource with an explicit deny"}
2023-06-04 05:16:53.333 - error: hoover.0 (1248) https://api-iot.he.services/commands/v1/context?macAddress=10-97-bd-01-b6-30&applianceType=WM&category=CYCLE
2023-06-04 05:16:53.333 - error: hoover.0 (1248) AxiosError: Request failed with status code 403
2023-06-04 05:16:53.333 - error: hoover.0 (1248) {"Message":"User is not authorized to access this resource with an explicit deny"}
2023-06-04 05:26:53.371 - error: hoover.0 (1248) https://api-iot.he.services/commands/v1/context?macAddress=10-97-bd-01-b6-30&applianceType=WM&category=CYCLE
2023-06-04 05:26:53.372 - error: hoover.0 (1248) AxiosError: Request failed with status code 403
2023-06-04 05:26:53.372 - error: hoover.0 (1248) {"Message":"User is not authorized to access this resource with an explicit deny"}
2023-06-04 05:36:53.386 - error: hoover.0 (1248) https://api-iot.he.services/commands/v1/context?macAddress=10-97-bd-01-b6-30&applianceType=WM&category=CYCLE
2023-06-04 05:36:53.386 - error: hoover.0 (1248) AxiosError: Request failed with status code 403
2023-06-04 05:36:53.386 - error: hoover.0 (1248) {"Message":"User is not authorized to access this resource with an explicit deny"}
2023-06-04 05:46:53.389 - error: hoover.0 (1248) https://api-iot.he.services/commands/v1/context?macAddress=10-97-bd-01-b6-30&applianceType=WM&category=CYCLE
2023-06-04 05:46:53.389 - error: hoover.0 (1248) AxiosError: Request failed with status code 403
2023-06-04 05:46:53.389 - error: hoover.0 (1248) {"Message":"User is not authorized to access this resource with an explicit deny"}
2023-06-04 05:56:53.342 - error: hoover.0 (1248) https://api-iot.he.services/commands/v1/context?macAddress=10-97-bd-01-b6-30&applianceType=WM&category=CYCLE
2023-06-04 05:56:53.342 - error: hoover.0 (1248) AxiosError: Request failed with status code 403
2023-06-04 05:56:53.342 - error: hoover.0 (1248) {"Message":"User is not authorized to access this resource with an explicit deny"}
2023-06-04 06:06:53.359 - error: hoover.0 (1248) https://api-iot.he.services/commands/v1/context?macAddress=10-97-bd-01-b6-30&applianceType=WM&category=CYCLE
2023-06-04 06:06:53.359 - error: hoover.0 (1248) AxiosError: Request failed with status code 403
2023-06-04 06:06:53.359 - error: hoover.0 (1248) {"Message":"User is not authorized to access this resource with an explicit deny"}
2023-06-04 06:16:53.391 - error: hoover.0 (1248) https://api-iot.he.services/commands/v1/context?macAddress=10-97-bd-01-b6-30&applianceType=WM&category=CYCLE
2023-06-04 06:16:53.391 - error: hoover.0 (1248) AxiosError: Request failed with status code 403
2023-06-04 06:16:53.391 - error: hoover.0 (1248) {"Message":"User is not authorized to access this resource with an explicit deny"}
2023-06-04 06:26:53.331 - error: hoover.0 (1248) https://api-iot.he.services/commands/v1/context?macAddress=10-97-bd-01-b6-30&applianceType=WM&category=CYCLE
2023-06-04 06:26:53.331 - error: hoover.0 (1248) AxiosError: Request failed with status code 403
2023-06-04 06:26:53.332 - error: hoover.0 (1248) {"Message":"User is not authorized to access this resource with an explicit deny"}
2023-06-04 06:36:53.389 - error: hoover.0 (1248) https://api-iot.he.services/commands/v1/context?macAddress=10-97-bd-01-b6-30&applianceType=WM&category=CYCLE
2023-06-04 06:36:53.389 - error: hoover.0 (1248) AxiosError: Request failed with status code 403
2023-06-04 06:36:53.389 - error: hoover.0 (1248) {"Message":"User is not authorized to access this resource with an explicit deny"}
2023-06-04 06:46:53.594 - error: hoover.0 (1248) https://api-iot.he.services/commands/v1/context?macAddress=10-97-bd-01-b6-30&applianceType=WM&category=CYCLE
2023-06-04 06:46:53.594 - error: hoover.0 (1248) AxiosError: Request failed with status code 403
2023-06-04 06:46:53.594 - error: hoover.0 (1248) {"Message":"User is not authorized to access this resource with an explicit deny"}
2023-06-04 06:56:53.367 - error: hoover.0 (1248) https://api-iot.he.services/commands/v1/context?macAddress=10-97-bd-01-b6-30&applianceType=WM&category=CYCLE
2023-06-04 06:56:53.367 - error: hoover.0 (1248) AxiosError: Request failed with status code 403
2023-06-04 06:56:53.367 - error: hoover.0 (1248) {"Message":"User is not authorized to access this resource with an explicit deny"}
2023-06-04 07:06:53.390 - error: hoover.0 (1248) https://api-iot.he.services/commands/v1/context?macAddress=10-97-bd-01-b6-30&applianceType=WM&category=CYCLE
2023-06-04 07:06:53.390 - error: hoover.0 (1248) AxiosError: Request failed with status code 403
2023-06-04 07:06:53.390 - error: hoover.0 (1248) {"Message":"User is not authorized to access this resource with an explicit deny"}
2023-06-04 07:16:53.355 - error: hoover.0 (1248) https://api-iot.he.services/commands/v1/context?macAddress=10-97-bd-01-b6-30&applianceType=WM&category=CYCLE
2023-06-04 07:16:53.355 - error: hoover.0 (1248) AxiosError: Request failed with status code 403
2023-06-04 07:16:53.355 - error: hoover.0 (1248) {"Message":"User is not authorized to access this resource with an explicit deny"}
2023-06-04 07:26:53.686 - error: hoover.0 (1248) https://api-iot.he.services/commands/v1/context?macAddress=10-97-bd-01-b6-30&applianceType=WM&category=CYCLE
2023-06-04 07:26:53.686 - error: hoover.0 (1248) AxiosError: Request failed with status code 403
2023-06-04 07:26:53.686 - error: hoover.0 (1248) {"Message":"User is not authorized to access this resource with an explicit deny"}
2023-06-04 07:36:53.434 - error: hoover.0 (1248) https://api-iot.he.services/commands/v1/context?macAddress=10-97-bd-01-b6-30&applianceType=WM&category=CYCLE
2023-06-04 07:36:53.434 - error: hoover.0 (1248) AxiosError: Request failed with status code 403
2023-06-04 07:36:53.434 - error: hoover.0 (1248) {"Message":"User is not authorized to access this resource with an explicit deny"}
2023-06-04 07:46:53.335 - error: hoover.0 (1248) https://api-iot.he.services/commands/v1/context?macAddress=10-97-bd-01-b6-30&applianceType=WM&category=CYCLE
2023-06-04 07:46:53.335 - error: hoover.0 (1248) AxiosError: Request failed with status code 403
2023-06-04 07:46:53.335 - error: hoover.0 (1248) {"Message":"User is not authorized to access this resource with an explicit deny"}
2023-06-04 07:56:53.590 - error: hoover.0 (1248) https://api-iot.he.services/commands/v1/context?macAddress=10-97-bd-01-b6-30&applianceType=WM&category=CYCLE
2023-06-04 07:56:53.590 - error: hoover.0 (1248) AxiosError: Request failed with status code 403
2023-06-04 07:56:53.591 - error: hoover.0 (1248) {"Message":"User is not authorized to access this resource with an explicit deny"}
2023-06-04 08:06:53.364 - error: hoover.0 (1248) https://api-iot.he.services/commands/v1/context?macAddress=10-97-bd-01-b6-30&applianceType=WM&category=CYCLE
2023-06-04 08:06:53.364 - error: hoover.0 (1248) AxiosError: Request failed with status code 403
2023-06-04 08:06:53.364 - error: hoover.0 (1248) {"Message":"User is not authorized to access this resource with an explicit deny"}
2023-06-04 08:16:53.378 - error: hoover.0 (1248) https://api-iot.he.services/commands/v1/context?macAddress=10-97-bd-01-b6-30&applianceType=WM&category=CYCLE
2023-06-04 08:16:53.378 - error: hoover.0 (1248) AxiosError: Request failed with status code 403
2023-06-04 08:16:53.379 - error: hoover.0 (1248) {"Message":"User is not authorized to access this resource with an explicit deny"}
2023-06-04 08:26:53.400 - error: hoover.0 (1248) https://api-iot.he.services/commands/v1/context?macAddress=10-97-bd-01-b6-30&applianceType=WM&category=CYCLE
2023-06-04 08:26:53.400 - error: hoover.0 (1248) AxiosError: Request failed with status code 403
2023-06-04 08:26:53.400 - error: hoover.0 (1248) {"Message":"User is not authorized to access this resource with an explicit deny"}
2023-06-04 08:36:53.364 - error: hoover.0 (1248) https://api-iot.he.services/commands/v1/context?macAddress=10-97-bd-01-b6-30&applianceType=WM&category=CYCLE
2023-06-04 08:36:53.366 - error: hoover.0 (1248) AxiosError: Request failed with status code 403
2023-06-04 08:36:53.366 - error: hoover.0 (1248) {"Message":"User is not authorized to access this resource with an explicit deny"}
2023-06-04 08:46:53.384 - error: hoover.0 (1248) https://api-iot.he.services/commands/v1/context?macAddress=10-97-bd-01-b6-30&applianceType=WM&category=CYCLE
2023-06-04 08:46:53.384 - error: hoover.0 (1248) AxiosError: Request failed with status code 403
2023-06-04 08:46:53.384 - error: hoover.0 (1248) {"Message":"User is not authorized to access this resource with an explicit deny"}
2023-06-04 08:56:53.428 - error: hoover.0 (1248) https://api-iot.he.services/commands/v1/context?macAddress=10-97-bd-01-b6-30&applianceType=WM&category=CYCLE
2023-06-04 08:56:53.428 - error: hoover.0 (1248) AxiosError: Request failed with status code 403
2023-06-04 08:56:53.428 - error: hoover.0 (1248) {"Message":"User is not authorized to access this resource with an explicit deny"}
2023-06-04 09:06:53.363 - error: hoover.0 (1248) https://api-iot.he.services/commands/v1/context?macAddress=10-97-bd-01-b6-30&applianceType=WM&category=CYCLE
2023-06-04 09:06:53.363 - error: hoover.0 (1248) AxiosError: Request failed with status code 403
2023-06-04 09:06:53.363 - error: hoover.0 (1248) {"Message":"User is not authorized to access this resource with an explicit deny"}
2023-06-04 09:16:53.397 - error: hoover.0 (1248) https://api-iot.he.services/commands/v1/context?macAddress=10-97-bd-01-b6-30&applianceType=WM&category=CYCLE
2023-06-04 09:16:53.397 - error: hoover.0 (1248) AxiosError: Request failed with status code 403
2023-06-04 09:16:53.397 - error: hoover.0 (1248) {"Message":"User is not authorized to access this resource with an explicit deny"}
2023-06-04 09:26:53.345 - error: hoover.0 (1248) https://api-iot.he.services/commands/v1/context?macAddress=10-97-bd-01-b6-30&applianceType=WM&category=CYCLE
2023-06-04 09:26:53.345 - error: hoover.0 (1248) AxiosError: Request failed with status code 403
2023-06-04 09:26:53.345 - error: hoover.0 (1248) {"Message":"User is not authorized to access this resource with an explicit deny"}
2023-06-04 09:36:53.368 - error: hoover.0 (1248) https://api-iot.he.services/commands/v1/context?macAddress=10-97-bd-01-b6-30&applianceType=WM&category=CYCLE
2023-06-04 09:36:53.368 - error: hoover.0 (1248) AxiosError: Request failed with status code 403
2023-06-04 09:36:53.369 - error: hoover.0 (1248) {"Message":"User is not authorized to access this resource with an explicit deny"}
2023-06-04 09:46:53.399 - error: hoover.0 (1248) https://api-iot.he.services/commands/v1/context?macAddress=10-97-bd-01-b6-30&applianceType=WM&category=CYCLE
2023-06-04 09:46:53.399 - error: hoover.0 (1248) AxiosError: Request failed with status code 403
2023-06-04 09:46:53.399 - error: hoover.0 (1248) {"Message":"User is not authorized to access this resource with an explicit deny"}
2023-06-04 09:56:53.365 - error: hoover.0 (1248) https://api-iot.he.services/commands/v1/context?macAddress=10-97-bd-01-b6-30&applianceType=WM&category=CYCLE
2023-06-04 09:56:53.365 - error: hoover.0 (1248) AxiosError: Request failed with status code 403
2023-06-04 09:56:53.365 - error: hoover.0 (1248) {"Message":"User is not authorized to access this resource with an explicit deny"}
2023-06-04 10:06:53.393 - error: hoover.0 (1248) https://api-iot.he.services/commands/v1/context?macAddress=10-97-bd-01-b6-30&applianceType=WM&category=CYCLE
2023-06-04 10:06:53.393 - error: hoover.0 (1248) AxiosError: Request failed with status code 403
2023-06-04 10:06:53.393 - error: hoover.0 (1248) {"Message":"User is not authorized to access this resource with an explicit deny"}
2023-06-04 10:16:53.419 - error: hoover.0 (1248) https://api-iot.he.services/commands/v1/context?macAddress=10-97-bd-01-b6-30&applianceType=WM&category=CYCLE
2023-06-04 10:16:53.419 - error: hoover.0 (1248) AxiosError: Request failed with status code 403
2023-06-04 10:16:53.419 - error: hoover.0 (1248) {"Message":"User is not authorized to access this resource with an explicit deny"}
2023-06-04 10:26:53.368 - error: hoover.0 (1248) https://api-iot.he.services/commands/v1/context?macAddress=10-97-bd-01-b6-30&applianceType=WM&category=CYCLE
2023-06-04 10:26:53.368 - error: hoover.0 (1248) AxiosError: Request failed with status code 403
2023-06-04 10:26:53.368 - error: hoover.0 (1248) {"Message":"User is not authorized to access this resource with an explicit deny"}
2023-06-04 10:36:53.379 - error: hoover.0 (1248) https://api-iot.he.services/commands/v1/context?macAddress=10-97-bd-01-b6-30&applianceType=WM&category=CYCLE
2023-06-04 10:36:53.380 - error: hoover.0 (1248) AxiosError: Request failed with status code 403
2023-06-04 10:36:53.380 - error: hoover.0 (1248) {"Message":"User is not authorized to access this resource with an explicit deny"}
2023-06-04 10:46:53.356 - error: hoover.0 (1248) https://api-iot.he.services/commands/v1/context?macAddress=10-97-bd-01-b6-30&applianceType=WM&category=CYCLE
2023-06-04 10:46:53.356 - error: hoover.0 (1248) AxiosError: Request failed with status code 403
2023-06-04 10:46:53.356 - error: hoover.0 (1248) {"Message":"User is not authorized to access this resource with an explicit deny"}
2023-06-04 10:56:53.366 - error: hoover.0 (1248) https://api-iot.he.services/commands/v1/context?macAddress=10-97-bd-01-b6-30&applianceType=WM&category=CYCLE
2023-06-04 10:56:53.366 - error: hoover.0 (1248) AxiosError: Request failed with status code 403
2023-06-04 10:56:53.367 - error: hoover.0 (1248) {"Message":"User is not authorized to access this resource with an explicit deny"}
2023-06-04 11:06:53.355 - error: hoover.0 (1248) https://api-iot.he.services/commands/v1/context?macAddress=10-97-bd-01-b6-30&applianceType=WM&category=CYCLE
2023-06-04 11:06:53.355 - error: hoover.0 (1248) AxiosError: Request failed with status code 403
2023-06-04 11:06:53.355 - error: hoover.0 (1248) {"Message":"User is not authorized to access this resource with an explicit deny"}
2023-06-04 11:16:53.394 - error: hoover.0 (1248) https://api-iot.he.services/commands/v1/context?macAddress=10-97-bd-01-b6-30&applianceType=WM&category=CYCLE
2023-06-04 11:16:53.394 - error: hoover.0 (1248) AxiosError: Request failed with status code 403
2023-06-04 11:16:53.394 - error: hoover.0 (1248) {"Message":"User is not authorized to access this resource with an explicit deny"}
2023-06-04 11:26:53.338 - error: hoover.0 (1248) https://api-iot.he.services/commands/v1/context?macAddress=10-97-bd-01-b6-30&applianceType=WM&category=CYCLE
2023-06-04 11:26:53.338 - error: hoover.0 (1248) AxiosError: Request failed with status code 403
2023-06-04 11:26:53.338 - error: hoover.0 (1248) {"Message":"User is not authorized to access this resource with an explicit deny"}
2023-06-04 11:36:53.359 - error: hoover.0 (1248) https://api-iot.he.services/commands/v1/context?macAddress=10-97-bd-01-b6-30&applianceType=WM&category=CYCLE
2023-06-04 11:36:53.360 - error: hoover.0 (1248) AxiosError: Request failed with status code 403
2023-06-04 11:36:53.360 - error: hoover.0 (1248) {"Message":"User is not authorized to access this resource with an explicit deny"}
2023-06-04 11:46:53.403 - error: hoover.0 (1248) https://api-iot.he.services/commands/v1/context?macAddress=10-97-bd-01-b6-30&applianceType=WM&category=CYCLE
2023-06-04 11:46:53.403 - error: hoover.0 (1248) AxiosError: Request failed with status code 403
2023-06-04 11:46:53.404 - error: hoover.0 (1248) {"Message":"User is not authorized to access this resource with an explicit deny"}
2023-06-04 11:54:27.877 - error: hoover.0 (66003) AxiosError: Request failed with status code 301
2023-06-04 11:54:27.877 - error: hoover.0 (66003) ""
2023-06-04 11:55:41.463 - error: hoover.0 (66035) AxiosError: Request failed with status code 301
2023-06-04 11:55:41.464 - error: hoover.0 (66035) ""
2023-06-04 13:15:55.089 - error: hoover.0 (66592) AxiosError: Request failed with status code 301
2023-06-04 13:15:55.089 - error: hoover.0 (66592) ""
2023-06-04 13:17:00.400 - debug: hoover.0 (66609) Redis Objects: Use Redis connection: <IP_ADDRESS>:9001
2023-06-04 13:17:00.456 - debug: hoover.0 (66609) Objects client ready ... initialize now
2023-06-04 13:17:00.458 - debug: hoover.0 (66609) Objects create System PubSub Client
2023-06-04 13:17:00.458 - debug: hoover.0 (66609) Objects create User PubSub Client
2023-06-04 13:17:00.554 - debug: hoover.0 (66609) Objects client initialize lua scripts
2023-06-04 13:17:00.557 - debug: hoover.0 (66609) Objects connected to redis: <IP_ADDRESS>:9001
2023-06-04 13:17:00.621 - debug: hoover.0 (66609) Redis States: Use Redis connection: <IP_ADDRESS>:9000
2023-06-04 13:17:00.653 - debug: hoover.0 (66609) States create System PubSub Client
2023-06-04 13:17:00.654 - debug: hoover.0 (66609) States create User PubSub Client
2023-06-04 13:17:00.763 - debug: hoover.0 (66609) States connected to redis: <IP_ADDRESS>:9000
2023-06-04 13:17:01.031 - debug: hoover.0 (66609) Plugin sentry Initialize Plugin (enabled=true)
2023-06-04 13:17:01.803 - error: hoover.0 (66609) AxiosError: Request failed with status code 301
2023-06-04 13:17:01.804 - error: hoover.0 (66609) ""
2023-06-04 13:17:53.671 - debug: hoover.0 (66609) Plugin sentry destroyed

Versions:

Adapter version: 0.0.7
JS-Controller version: 4.0.24
Node version:  v16.20.0
Operating system: debian bullseye

Additional context
Same on my second Server with Arch Linux and Node version 18
with kind regards
Bernd

please try 0.1.0

please try 0.1.0

Moin,
nop, I get other errors.
2023-06-05 09:35:39.712 - info: host.iobroker iobroker url TA2k/ioBroker.hoover --host iobroker --debug
2023-06-05 09:36:08.793 - debug: hoover.0 (75226) Redis Objects: Use Redis connection: <IP_ADDRESS>:9001
2023-06-05 09:36:08.856 - debug: hoover.0 (75226) Objects client ready ... initialize now
2023-06-05 09:36:08.857 - debug: hoover.0 (75226) Objects create System PubSub Client
2023-06-05 09:36:08.858 - debug: hoover.0 (75226) Objects create User PubSub Client
2023-06-05 09:36:08.953 - debug: hoover.0 (75226) Objects client initialize lua scripts
2023-06-05 09:36:08.956 - debug: hoover.0 (75226) Objects connected to redis: <IP_ADDRESS>:9001
2023-06-05 09:36:09.021 - debug: hoover.0 (75226) Redis States: Use Redis connection: <IP_ADDRESS>:9000
2023-06-05 09:36:09.049 - debug: hoover.0 (75226) States create System PubSub Client
2023-06-05 09:36:09.050 - debug: hoover.0 (75226) States create User PubSub Client
2023-06-05 09:36:09.151 - debug: hoover.0 (75226) States connected to redis: <IP_ADDRESS>:9000
2023-06-05 09:36:09.436 - debug: hoover.0 (75226) Plugin sentry Initialize Plugin (enabled=true)
2023-06-05 09:36:10.663 - debug: hoover.0 (75226) "\n \n\n\n\n\n\n
2023-06-05 09:36:10.664 - debug: hoover.0 (75226) fwuid: {"mode":"PROD","app":"siteforce:loginApp2","serializationVersion":"1-244.20.1-2.41.4-b","parts":"f","loaded":{"APPLICATION@markup://siteforce:loginApp2":"Izv9eREiUIuimW-V5PtbgQ"},"dns":"c","fwuid":"emxZN2gzQnZ0X3FSYS1kQnBRbHV4QWI4T1Q3UVpoR0gtemxDX3B4aTM3bVEyNDQuMjAuMS0yLjQxLjQ"}
2023-06-05 09:36:10.865 - debug: hoover.0 (75226) {"actions":[{"id":"106;a","state":"SUCCESS","returnValue":null,"error":[]}],"context":{"mode":"PROD","app":"siteforce:loginApp2","contextPath":"/s/sfsites","pathPrefix":"","fwuid":"emxZN2gzQnZ0X3FSYS1kQnBRbHV4QWI4T1Q3UVpoR0gtemxDX3B4aTM3bVEyNDQuMjAuMS0yLjQxLjQ","mlr":1,"loaded":{"APPLICATION@markup://siteforce:loginApp2":"Izv9eREiUIuimW-V5PtbgQ"},"globalValueProviders":[{"type":"$Global","values":{"eswConfigDeveloperName":{"writable":true,"defaultValue":""},"isVoiceOver":{"writable":true,"defaultValue":false},"setupAppContextId":{"writable":true,"defaultValue":""},"density":{"writable":true,"defaultValue":""},"srcdoc":{"writable":false,"defaultValue":false},"appContextId":{"writable":true,"defaultValue":""},"dynamicTypeSize":{"writable":true,"defaultValue":""}}}],"enableAccessChecks":true,"apce":1,"dns":"c","lairn":[],"laerc":[],"lav":"58","mna":{"lightning":"interop"},"lff":{"ENABLE_MIXED_SHADOW_MODE":false,"ENABLE_LIGHT_GET_ROOT_NODE_PATCH":true,"DISABLE_LIGHT_DOM_UNSCOPED_CSS":false},"arse":1,"acaf":1,"services":["markup://lightning:configProvider","markup://force:salesforceScopedModuleResolver","markup://force:ldsEngineCreator","markup://instrumentation:locatorService"]},"events":[{"descriptor":"markup://aura:clientRedirect","attributes":{"values":{"url":"https://account2.hon-smarthome.com/secur/frontdoor.jsp?allp=1&apv=1&cshc=8000003AgcM0000000Lkcq&refURL=https%3A%2F%2Faccount2.hon-smarthome.com%2Fsecur%2Ffrontdoor.jsp&retURL=%2Fsetup%2Fsecur%2FRemoteAccessAuthorizationPage.apexp%3Fsource%3DCAAAAYiPontSMDAwMDAwMDAwMDAwMDAwAAAA9BxY18MSoE37Qd7gmh-5bPaV6rNjdchJoOP92cTlQp8rYHsaJRokB83by9jB2NdiglxwUOj44jobixAraiUpo_5tT-UU-z2PJV7UlfcQ2m51WhIUNKhKIQNUXHsSAi2Z5tBs_5S05NAvekOuGdwDbh6Gt_tzO4cY3qllLbI-5bIba8SHLS-KNhjxG4GanaKNVz7HL3pU6SlTBu_H_hVHRBZ7pMQxvdyG3idZ3aRarisaO2vKTuRLO3jZrn9cBSd2Qiilzl5yM0BdGJNYCqWGUca5L6l1PEZL3fAJAPQuo1KzzsbjjS7Q5y6qd0FFea22TRJEzNGOtCFn7B2hG7ad0cBKiGlNMOmX1Rzv8X_bh1QyhTuVnaDxYllC_gbW4k3xyiJd2QDRwejQX1NmnyNvrVcb72GyEb-AtM3IjTh1xhKXRXZCIRzA0X90SIc-xoBpRk1He7qVfKAzhagiSMKFm9mXUfMOtO-htNmUnaUBua9uXUyzyXnUiIelKrIBaJSmvwWgAXxqxyfqi-8fO88lH651Crm1wSu4ADQrq1zcZwzqFkejrJ6no8bmYZtemRLktMyw7BVaNEgz8LqcH69QOwNBaMTz-vKzGBDNn6tCyoTvM5RREfBsYNg52a3z6T1XNAM8kpv0Gtg_XUEQZndef8law7-Hu35YosrWuRyhYtASr9_qnJqCc1H8HjKr5Uscgn9j-y_kSbL4zUvMb5EK6nHLSXnJXVnT2_lW0aWoJ2DB%26display%3Dtouch&sid=00DU0000000Lkcq%21ARUAQJXBPFtCAnFCklNuilGWiqztYzL0Du2BilAnDE.20ljEQo3bH1Uy7CjHK.l4v9rOgAbPrmNRuewdjXqYDbDcJB80tTKe&untethered="}}}],"perfSummary":{"version":"core","request":9,"actions":{"106;a":{"total":5,"db":2}},"actionsTotal":5,"overhead":0}}
2023-06-05 09:36:11.001 - debug: hoover.0 (75226) "\r\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n"
2023-06-05 09:36:11.508 - debug: hoover.0 (75226) "\r\n\n\n\n \n\n\n\n\n\n\n\n\n\n\n\n\n"
2023-06-05 09:36:11.956 - debug: hoover.0 (75226) "
2023-06-05 09:36:11.957 - error: hoover.0 (75226) Missing step4 url
2023-06-05 09:36:11.957 - error: hoover.0 (75226) "

if you need anything else, just ask.
VG
Bernd

I need the account via mail
<EMAIL_ADDRESS>

I need the account via mail<EMAIL_ADDRESS>
Moin,
I have sent it to your mail address.
VG
Bernd

Moin,
As you said in your email, I reinstalled it via github.
After that I also did an upload from "ioBroker", the connection works and the adapter turns green again.
On my second ioBroker installation, I only installed version 0.1.0, after that the adapter was yellow with an exclamation mark, after an upload from the ioBroker and refresh of the adapter it was green again.
For me, it works now, but only after I did after install an upload.
Thank you for responding quickly and solving the problem
VG
Bernd

Hi,
i have the same Problem with Hoover-Wizard Login. Axios Error Code 301.


state=finished raised RateLimitError

tenacity.RetryError: RetryError[<Future at 0x1c7385c4820 state=finished raised RateLimitError>]

paste all terminal output

Hello,
When you're troubleshooting the error in the program, you should investigate the line before
The above exception was the direct cause of the following exception:

Traceback (most recent call last):

in the terminal output. This line usually contains the exact statement that led to the error and will be crucial for identifying the root cause of the problem.
If you have any specific questions or require further assistance, do not hesitate to raise them! Thank you for your support and interest in ChatDev.


Add optional support for VTune profiling

VTune has proved to be really useful when it comes to profiling on x86. Unfortunately, one of the current limitations is that VTune is not able to deal with dynamic code automatically so it can't find the code coming from our VM. To fix this, we should use its JIT Profiling API in IREE to notify VTune when the binary is loaded.
We can take a look at how this is done in LLVM for MCJit and oneDNN.
@benvanik, do you think you could help with this?
FYI: @jpienaar, @MaheshRavishankar, @bjacob, @hanhanW, @mattwalsh

Is this something that could fit under the tracing API? (Those are intended to be stubbed out and allow for different "tracers"). Is this just for loading or what other events need to be generated?

Yeah, mostly for loading:

The following values are allowed for event_type:

iJVM_EVENT_TYPE_METHOD_LOAD_FINISHED
Send this notification after a JITted method has been loaded into memory, and possibly JIT compiled, but before the code is executed. Use the iJIT_Method_Load structure for EventSpecificData. The return value of iJIT_NotifyEvent is undefined.

iJVM_EVENT_TYPE_SHUTDOWN
Send this notification to terminate profiling. Use NULL for EventSpecificData. iJIT_NotifyEvent returns 1 on success.

JVM_EVENT_TYPE_METHOD_UPDATE
Send this notification to provide new content for a previously reported dynamic code. The previous content will be invalidated starting from the time of the notification. Use the iJIT_Method_Load structure for EventSpecificData with the following required fields:method_id to identify the code to updatemethod_load_address to specify the start address within an identified code range where the update should be startedmethod_size to specify the length of an updated code range

JVM_EVENT_TYPE_METHOD_INLINE_LOAD_FINISHED
Send this notification when an inline dynamic code is JIT compiled and loaded into memory by the JIT engine, but before the parent code region starts executing. Use the iJIT_Method_Inline_Load structure for EventSpecificData.

iJVM_EVENT_TYPE_METHOD_LOAD_FINISHED_V2
Send this notification when a dynamic code is JIT compiled and loaded into memory by the JIT engine, but before the code is executed. Use the iJIT_Method_Load_V2 structure for EventSpecificData.

@jpienaar @mattwalsh Need an owner for this if it is truly a P0 item

I'm a little confused; I thought this VTune work would allow it to find & disassemble the associated binary code in our IREE binaries.  If we compiled with the API would that actually enable that to happen?  As I read the event descriptions I'm not quite getting how that would then all just work.
Assuming it would work, is there a sense of how much work we'd have to do, and if it could be added on (vs made to be permanent part of the compiler w/ new dependencies)?

If we compiled with the API would that actually enable that to happen?

Yes, that's the idea.

is there a sense of how much work we'd have to do, and if it could be added on (vs made to be permanent part of the compiler w/ new dependencies)?

I don't have a good understanding of the runtime/vm but I guess it's a matter of registering a iJVM_EVENT_TYPE_METHOD_LOAD_FINISHED event after loading the binary and before executing it? It doesn't look like we have to do anything else... but I'm not sure.
In terms of dependencies, we would need either:

a CMake variable to provide the VTune installation path, include the API header to invoke the method to register the event and link against the VTune library, or
a generic interface/API to register this kind of events within IREE and then provide the VTune specific implementation externally...

I understand the latter is what @jpienaar means by the "tracing API"? I don't know much about that.

Can we get an update on this P0 issue? (Is it P0?)

Maybe not P0

Things may just work if you switch to using the system linker as that dlopen's/loadlibrary's native elfs/dlls/etc - tracy and perf both support working like this so I'd assume vtune would too.
We can still add optional support to the embedded ELF loader for their API, though, and it should be fairly easy to do for the top level entry points but won't have all of the information a real library would (we only know about external entry points and not any internal functions - like libc calls - that are inside of the loaded ELFs).
We shouldn't need to add any deps as we'll be dynamically loading the library and can always have it enabled on x86/64 builds of the runtime when not size-optimized.

Annoyingly vtune doesn't work at all on AMD CPUs, and AMD's uprof doesn't have documented JIT APIs (but does have them (AMDTJitProfileMethodLoad in AMDJITProfileAgent.dll/etc), so I'll see if I can get a patch together but will need to find a way to test things.

Awesome! Thanks a lot, Ben!

Things may just work if you switch to using the system linker as that dlopen's/loadlibrary's native elfs/dlls/etc

Yeah, that's what I've been doing in general for profiling but it doesn't seem to work for VTune. I tried with the same compilation configuration and I could only see the assembly with perf.

Assigning this to @penpornk as she is currently driving the discussion with Intel about related issues.


Error When Switching from Debug to Release Mode in VS2022

I am using Visual Studio 2022 17.0.4 on Windows 10
When I am following the instructions in Extra Section 2.1 Preparing for Analysis , it required making a release-mode build of the project. However, when I switch to a release build, the Linker failed to open the input files.
The output says it fail to generate the projects imgui, glfw, basisu, and nvpro_core with error value cannot be null and parameter name path1

Update:
According to Error: Value cannot be nul
It is fixed after restarting VS. I am not sure the reason of this problem, which could be a bug of VS2022

Interesting! I haven't tested this on Visual Studio 2022 yet, so it could be a bug with that. My initial guess was going to be that the imgui, glfw, and basisu submodules weren't downloaded (running git submodule update --init --recursive in nvpro_core would fix that), but glad you were able to solve it!


SwiftRuntimeSupport 0.2.1 give empty SwiftSupport folder

Since i have updated to the 0.2.1 version of SwiftRuntimeSupport, we have this following error from Apple :

"ITMS-90424: Invalid Swift Support - The SwiftSupport folder is empty. Rebuild your app using the current public (GM) version of Xcode and resubmit it."

I have check into the SwiftSupport folder of my .xcarchive and it contains an iphoneos but this one is empty.
So i have search into the logs on an archive, into the task of the SwiftRuntimeSupport : "_SRSCopySwiftDependencies"
I can see that the 0.2.0 copy the required dylib and the 0.2.1 not.
The difference beetween the two is the path of the swift version :
"Toolchains/XcodeDefault.xctoolchain/usr/lib/swift-5.0/iphoneos" for the 0.2.0
"Toolchains/XcodeDefault.xctoolchain/usr/lib/swift-5.5/iphoneos" for the 0.2.1
It's consistent with this modification  onto the iOS/SwiftRuntimeSupport/source/SwiftRuntimeSupport.targets.
But if we look into the swift-5.5/iphoneos folder we can see that all the dylib of Apple is missing and only contains "libswift_Concurrency.dylib"
So it's seems that Apple have changed the SwiftSupport systeme and that the _SRSCopySwiftDependencies actually not adapted for this new system
PS : The logs
log_2_0.txt
log_2_1.txt

Experience the same problem when trying to deploy a build with updated SwiftRuntimeSupport package to the App Store.

Same here, _SRSCopySwiftDependencies does not copy Swift dylibs when archiving.
Target "_SRSCopySwiftDependencies" in file "/Users/user/.nuget/packages/xamarin.ios.swiftruntimesupport/0.2.1/buildTransitive/Xamarin.iOS.SwiftRuntimeSupport.targets":
  Task "Message"
    Copying Swift Frameworks dependencies for bin/iPhoneSimulator/Debug/device-builds/ipad (5th generation)-11.4/App.iOS.app/App.iOS to the bin/iPhoneSimulator/Debug/device-builds/ipad (5th generation)-11.4/App.iOS.app/Frameworks folder.
  Done executing task "Message".
  Task "Exec" skipped, due to false condition; ('$(_CodeSigningKey)' != '') was evaluated as ('' != '').
  Using "Exec" task from assembly "/Library/Frameworks/Mono.framework/External/xbuild/Xamarin/iOS/../iOS/Xamarin.iOS.Tasks.dll".
  Task "Exec"
    /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator15.2.sdk/../../../../../Toolchains/XcodeDefault.xctoolchain/usr/bin/swift-stdlib-tool --copy --verbose                             --scan-executable 'bin/iPhoneSimulator/Debug/device-builds/ipad (5th generation)-11.4/App.iOS.app/App.iOS' --scan-folder 'bin/iPhoneSimulator/Debug/device-builds/ipad (5th generation)-11.4/App.iOS.app/Frameworks/' --scan-folder 'bin/iPhoneSimulator/Debug/device-builds/ipad (5th generation)-11.4/App.iOS.app/PlugIns/' --platform 'iphonesimulator' --toolchain '/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator15.2.sdk/../../../../../Toolchains/XcodeDefault.xctoolchain/' --destination 'bin/iPhoneSimulator/Debug/device-builds/ipad (5th generation)-11.4/App.iOS.app/Frameworks/' --resource-destination 'bin/iPhoneSimulator/Debug/device-builds/ipad (5th generation)-11.4/App.iOS.app/' --resource-library libswiftRemoteMirror.dylib --unsigned-destination 'obj/iPhoneSimulator/Debug/device-builds/ipad (5th generation)-11.4/SwiftSupport' --strip-bitcode --strip-bitcode-tool '/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator15.2.sdk/../../../../../Toolchains/XcodeDefault.xctoolchain/usr/bin/bitcode_strip' --emit-dependency-info 'obj/iPhoneSimulator/Debug/device-builds/ipad (5th generation)-11.4/SwiftStdLibToolInputDependencies.dep' --source-libraries '/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator15.2.sdk/../../../../../Toolchains/XcodeDefault.xctoolchain/usr/lib/swift-5.5/iphonesimulator'
  Done executing task "Exec".
Done building target "_SRSCopySwiftDependencies" in project "App.iOS.csproj".


⚠ GitLab Server has degraded performance

In 1c14829, GitLab Server (https://gitlab01.its-telekom.eu) experienced degraded performance:

HTTP code: 200
Response time: 11813 ms

Resolved: GitLab Server performance has improved in a8ce611.


not work in firefox 32 bit system

Auto click not work for me since last night.There is no option for adding a link.
Please give me solution

We are no longer supporting firefox for now.

why i need firefox


Fix flaky tests in SMTPMailSenderTest.java and ReflectionToStringBuilderUtilsTest.java

Description
The tests below in ReflectionToStringBuilderUtilsTest.java and SMTPMailSenderTest.java were found flaky because of the ordering of HashSet and result Arrays. The orders of elements in the HashSet and result Arrays are not the same every time the test being called. In this case, LinkedHashSet was applied and Arrays were sorted to ensure the orders do not cause the flakiness. This code change is trying to fix the flaky tests mentioned above, because they sometimes fail (as the picture showed) and sometimes pass. The failure could be reproduced by the commands below by using the tool of NonDex. The code change is to make sure the tests will always pass in this case.

org.apache.cloudstack.utils.mailing.SMTPMailSenderTest.setMailRecipientsTest
org.apache.cloudstack.utils.reflectiontostringbuilderutils.ReflectionToStringBuilderUtilsTest.validateGetNonSelectedFieldsObjectIsACollectionAndValidSelectedFieldsMustReturnNonSelectedFields
org.apache.cloudstack.utils.reflectiontostringbuilderutils.ReflectionToStringBuilderUtilsTest.validateGetNonSelectedFieldsObjectIsNotACollectionAndValidSelectedFieldsMustReturnNonSelectedFields

Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[x] Bug fix (non-breaking change which fixes an issue)
[ ] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)

Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale

[ ] Major
[ ] Minor

Bug Severity

[ ] BLOCKER
[ ] Critical
[ ] Major
[x] Minor
[ ] Trivial

Screenshots (if appropriate):

How Has This Been Tested?

The test failures could be reproduced by

mvn install -pl utils -am -DskipTests
run tests with NonDex
mvn -pl utils edu.illinois:nondex-maven-plugin:2.1:nondex -Dtest=org.apache.cloudstack.utils.mailing.SMTPMailSenderTest#setMailRecipientsTest

@DaanHoogland a Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

Packaging result: :heavy_check_mark: el7 :heavy_check_mark: el8 :heavy_check_mark: debian :heavy_check_mark: suse15. LL-JID 223


Recurrent models should accept nonzero initial state

To sample sequentially from a recurrent model, it would be useful to add some API for accepting an initial hidden state and running the model forward one time step.

:+1: , really looking forward


Downloading from /icons has different SVG's than downloading from Web.

Prerequisites

Version: Latest (N/A)
Are you running from source/main: Yes (N/A)
Are you using a released build: N/A
Operating system: N/A

Step to reproduce

Download any Icon from the raw.github endpoint.

Import that icon into XCode manually. Notice that the SVG is not visible/usable. I also attempted to set the rendering mode and toyed around with any of the Contents.JSON options however nothing will make them usable.

Download any Icon from www.iconoir.com and then import into XCode, works as expected.

This Script, is currently broken, but it's what made the problem obvious. The intention here is to have all of the icons downloaded and then added as an asset to a project, but for obvious reasons it's not working. The script is NOT the problem, I already tested it without using the script, by manually performing the steps that the script does, and the issue still persists.
https://gist.github.com/mkaulfers/2200dcfa76bad800823eca0e975103f6
Additional info or screenshots

Is there any form of processing happening on the web side with these icons? If there is, can we modify that to have some pre-processing Workflow to process it before adding to the repo, or show what that processing action is so that I can update my script to handle it.

StackOverflow Question

Difference is that the files downloaded from the website contain an XML declaration (see https://oreillymedia.github.io/Using_SVG/extras/ch01-XML.html): <?xml version="1.0" encoding="UTF-8"?>
It seems like XCode or the tools you rely on in your scripts require this XML declaration in order to interpret the files correctly. So you might want to add this XML declaration to the files inside your script.

@paescuj No that doesn't seem to be the cause of it.
<?xml version="1.0" encoding="UTF-8"?>
<svg width="24" height="24" stroke-width="1.5" viewBox="0 0 24 24" fill="none" xmlns="http://www.w3.org/2000/svg">
<path d="M14.2718 10.445L18 2M9.31612 10.6323L5 2M12.7615 10.0479L8.835 2M14.36 2L13.32 4.5M6 16C6 19.3137 8.68629 22 12 22C15.3137 22 18 19.3137 18 16C18 12.6863 15.3137 10 12 10C8.68629 10 6 12.6863 6 16Z" stroke="currentColor" stroke-linecap="round" stroke-linejoin="round"/>
<path d="M10.5 15L12.5 13.5V18.5" stroke="currentColor" stroke-linecap="round" stroke-linejoin="round"/>
</svg>

Oh right, also currentColor gets replaced by the selected color on the website which is usually #000000:
https://github.com/iconoir-icons/iconoir/blob/7adad51d3d9bbc7964d70a3891d6d4c04b6ddacd/iconoir.com/components/Icon.tsx#L16-L22

@paescuj so the issue wasn't the XML tags, it is actually the current-color and stroke width tags that ended up fixing it. Good callout, however shouldn't we have these set as a default value in the repository, and only change it as needed when downloading? I fail to see why we'd keep them without those values being set. Thanks!

No, I don't think so. That's actually inteded so the color isn't hard-coded and adapts to the current color in the browser.


add ability for user to handle error in their own way while providing a default error handler

the default handler provides the same functionality as current module

test?

@danmactough added test.


fix(artifacts): Artifacts: properties cleanup

Fixes WB-13706
Description

artifact.entity, artifact.project raises an exception until the artifact is saved. Before, they returned some value that was never used and usually different than the project the artifact ended up being saved in. See discussion here.
artifact.name uses the secondary (portfolio) collection. Before, it used the primary (sequence) collection. See discussion here.
Artifact.from_id sets the artifact name to the primary (sequence) collection name + version. Before, it set the artifact name to the <collection>:<alias> of the first non-"latest" alias. See discussion here.
artifact.full_name renamed to artifact.qualified_name. See discussion here.

Test plan

/fix-title


[Model Request] Microsoft Phi-3 mini Instruct (Faster and better then LLama 3 8B)

⚙  Request New Models

Link to an existing implementation (e.g. Hugging Face/Github):

[ ] - Default version (faster) https://huggingface.co/microsoft/Phi-3-mini-4k-instruct

[ ] - GGUF model: https://huggingface.co/PrunaAI/Phi-3-mini-128k-instruct-GGUF-Imatrix-smashed

Is this model architecture supported by MLC-LLM? (the list of supported models)  Yes

Additional context

This model is the replacement model of Phi-2 it is better on all the benchmarks then LLama 3 8B, while beeing much smaller. It's kinda of cool that this is even possible on a phone now. I hope it will be quickly available on Android MLC chat.
Note: phi-3 mini will have a bigger brother next month called "phi-3 small" that one will even compete with the 70billion model and better then GPT 3.5
ps: android bug: when a user downloaded a model, and wants to delete the downloaded model, the android application also deletes the Model from the list. This is really bad, because users can't  re-download the model anymore . It doesn't re-download the supported models. Maybe you should foresee a possibility to refresh the list of supported models that you compiled?

There is a WIP PR: https://github.com/mlc-ai/mlc-llm/pull/2222

Oh yes I see.
I've been paying with phi 3 on my pc and it is insane how good this model
is. It beats gpt 3.5 on everything I throw at it. How do they do this in
such a small file.
ps: there was a Jenkins error: pr- merge this commit cannot be build
On Sun, 28 Apr 2024, 07:40 Siyuan Feng, @.***> wrote:

There is a WIP PR: #2222 https://github.com/mlc-ai/mlc-llm/pull/2222
—
Reply to this email directly, view it on GitHub
https://github.com/mlc-ai/mlc-llm/issues/2238#issuecomment-2081340831,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB7MPQRGARYX57A75YD7BB3Y7SDWLAVCNFSM6AAAAABG37Q432VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBRGM2DAOBTGE
.
You are receiving this because you authored the thread.Message ID:
@.***>

We have merged the Phi support early this week, so let's close this issue.

How can we run phi-3 ?I don't see it in my models list.
Is there a new apk file? Or is there a refresh button to load the new list of models within the app?


Consider moving the preview to before the filter

Will need to think about how this works - probably need a preview button

this I meant specifically on the Welcome page - probably clear but just didn't wnat to accidentally cause work!


Add document for installing with cli

This is a requirement from CP4APP to install ibm common service operator from the command line

@chenzhiwei @DanielXLee
CP4App and CP4Auto request an installation document executed by CLI.
Please review.


New version: TSML v2.0.0

Registering package: TSML
Repository: https://github.com/IBM/TSML.jl
Created by: @ppalmes
Version: v2.0.0
Commit: 9176388f103be51c9d9651f3b1df38b8172adcc7
Reviewed by: @ppalmes
Reference: https://github.com/IBM/TSML.jl/issues/39#issuecomment-493912861

Can you add
[compat]
julia = "1"

to your project file and retrigger the bot?

thanks, just retriggered the bot


Synced archotech teleporter from VFE-Insectoids

Requires #423 to work.
Took a few days longer than I've expected due to some complexity caused by how the mod implemented the accept button, but here it is.

Synced the archotech teleporter code with use of sessions
Separated the patch into regions
Created a Shared language file, moved MpVehiclesSwitchToMap there and renamed it to MpCompatSwitchToMap
Created a language file for VFE-Insectoids
Changed MpVehiclesSwitchToMap to MpCompatSwitchToMap in Vehicle Framework compat

When it gets too complex, don't shy away from doing a PR to them to make it easier here. I believe VE team welcomes patches just fine.


fixed multiple realms selection

and changed OS to pass warden check

Let's merge #120 first, as that contains the fix for allowing multiple realms to be handled correctly. It seems to be included in here, but it's difficult to see what's new.
After that we can have a look at the Win vs OSX identifier, as well as Trinity requiring a realm ID to be passed in.

i've splitted commit and changed that minor code-style

could you accept this PR? it is fully working

#120 was merged, which contained the original fix for supporting multiple realms.
Could you rebase this on top of current master only including the TrinityCore fixes?

Splitted in:
https://github.com/wowserhq/wowser/pull/165
https://github.com/wowserhq/wowser/pull/166

Thanks 👍


[Bug] doris 1.2.3 function char trim error

Search before asking

[X] I had searched in the issues and found no similar issues.

Version
Server version: 5.7.99 Doris version doris-1.2.3-rc02-Unknown
client version: mysql  Ver 8.0.30 for Linux on x86_64 (Source distribution)
What's Wrong?
mysql> select trim('ababccaab','ab') str;
ERROR 1105 (HY000): errCode = 2, detailMessage = No matching function with signature: trim(varchar(-1), varchar(-1)).
mysql> select char(10) as str;
ERROR 1105 (HY000): errCode = 2, detailMessage = No matching function with signature: char(tinyint(4)).
What You Expected?
function worked as doc says
How to Reproduce?
No response
Anything Else?
No response
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

you can try 1.2.6

tried, the same result

example sql "select char(15049882, 15179199, 14989469);" does not work,
SQL Error [1105] [HY000]: errCode = 2, detailMessage = No matching function with signature: char(int(11), int(11), int(11)).
https://doris.apache.org/zh-CN/docs/dev/sql-manual/sql-functions/string-functions/char
mysql> select char(68, 111, 114, 105, 115);
+--------------------------------------+
| char('utf8', 68, 111, 114, 105, 115) |
+--------------------------------------+
| Doris                                |
+--------------------------------------+

mysql> select char(15049882, 15179199, 14989469);
+--------------------------------------------+
| char('utf8', 15049882, 15179199, 14989469) |
+--------------------------------------------+
| 多睿丝                                     |
+--------------------------------------------+

mysql> select char(255);
+-------------------+
| char('utf8', 255) |
+-------------------+
| NULL              |
+-------------------+

now 2.0 solved


[contracts] Connext becomes AMM

In order to save gas, the Connext contract should extend the StableSwap contract. This allows us to avoid an approve, transfer, and transferFrom for both xcall and execute.
Must:

[ ] Retain the ability to add an external AMM if needed
[ ] Expose the ability to supply/withdraw funds from the AMM via Connext
[ ] Update the balances for the AMM via Connext

whoops duplicate of #970


Async queries sometimes fail when retrieving cached query results

This bug effects both the polling and WebSocket implementations of the async queries experience introduced in SIP-39.
Expected results
When clients are notified of query completion (either by polling or WS message), they should be able to retrieve the results of that query using the result_url value the server gave them. The server should respond with a 200 and the cached query results. This should be the case for all charts in Superset.
Actual results
When a client is notified the query has completed, the client initiates the call to the backend with the result_url. For some charts, the server is responding with a 400 bad request because it could not find the cached results.
Screenshots

How to reproduce the bug
There are a few charts/dashboards where this is happening. One example is:

With the GLOBAL_ASYNC_QUERIES feature flag turned on, using either websocket or polling transport...
Visit /superset/dashboard/deck/
Notice that after some time, all charts render an "Unexpected error" message.

Environment
Latest master

Pinging/assigning @villebro since he might be well positioned to validate that this bug is behind us. That said, I'm optimistic that this was closed by https://github.com/apache/superset/pull/14291 and left open unintentionally. I'll close it as stale, just to be safe, and I'm more than happy to reopen this if anyone thinks it's warranted.


fix sphinx errors

Fixed sphinx errors but this work is WIP.
Some warnings are still remain because;

__init__.py is not defined correctly.  #182
Equations in developer_guide/custom_optimizer.md
is not rendered correctly as html.
I couldn't remove WARNING: Definition list ends without a blank line; unexpected unindent. arise from docstring of aiaccel.config.BaseConfig.get_property.

All of warnings and errors on docs-building are removed.
Note, some of extention and configurations are added to docs/source/conf.py.


TimeStampedModel breaks django migrations in version 1.5.6

I upgraded from 1.5.5 to 1.5.6 and now whenever I try to run makemigrations the following error occurs for models that inherit TimeStampedModel:
ValueError: Cannot serialize: <class django.db.models.fields.NOT_PROVIDED at 0x1076a7ae0>
There are some values Django cannot serialize into migration files.
For more, see https://docs.djangoproject.com/en/dev/topics/migrations/#migration-serializing

It seems to be related to the "default" value of the DateTimeField and occurs during in the Django migration system.
The change that causes the problem is here:
https://github.com/django-extensions/django-extensions/compare/1.5.5...1.5.6#diff-8e3fa7c3b02c3419c7374340925fe214L202
Tested to affect Django 1.7.4 up to 1.8.4
Full stack trace
Traceback (most recent call last):
  File "./manage.py", line 10, in <module>
    execute_from_command_line(sys.argv)
  File "/Volumes/Krieger/Users/zeraien/Development/ingager/results/env-ingager_results/lib/python2.7/site-packages/django/core/management/__init__.py", line 385, in execute_from_command_line
    utility.execute()
  File "/Volumes/Krieger/Users/zeraien/Development/ingager/results/env-ingager_results/lib/python2.7/site-packages/django/core/management/__init__.py", line 377, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/Volumes/Krieger/Users/zeraien/Development/ingager/results/env-ingager_results/lib/python2.7/site-packages/django/core/management/base.py", line 288, in run_from_argv
    self.execute(*args, **options.__dict__)
  File "/Volumes/Krieger/Users/zeraien/Development/ingager/results/env-ingager_results/lib/python2.7/site-packages/django/core/management/base.py", line 338, in execute
    output = self.handle(*args, **options)
  File "/Volumes/Krieger/Users/zeraien/Development/ingager/results/env-ingager_results/lib/python2.7/site-packages/django/core/management/commands/makemigrations.py", line 124, in handle
    self.write_migration_files(changes)
  File "/Volumes/Krieger/Users/zeraien/Development/ingager/results/env-ingager_results/lib/python2.7/site-packages/django/core/management/commands/makemigrations.py", line 152, in write_migration_files
    migration_string = writer.as_string()
  File "/Volumes/Krieger/Users/zeraien/Development/ingager/results/env-ingager_results/lib/python2.7/site-packages/django/db/migrations/writer.py", line 132, in as_string
    operation_string, operation_imports = OperationWriter(operation).serialize()
  File "/Volumes/Krieger/Users/zeraien/Development/ingager/results/env-ingager_results/lib/python2.7/site-packages/django/db/migrations/writer.py", line 88, in serialize
    arg_string, arg_imports = MigrationWriter.serialize(arg_value)
  File "/Volumes/Krieger/Users/zeraien/Development/ingager/results/env-ingager_results/lib/python2.7/site-packages/django/db/migrations/writer.py", line 334, in serialize
    return cls.serialize_deconstructed(path, args, kwargs)
  File "/Volumes/Krieger/Users/zeraien/Development/ingager/results/env-ingager_results/lib/python2.7/site-packages/django/db/migrations/writer.py", line 240, in serialize_deconstructed
    arg_string, arg_imports = cls.serialize(arg)
  File "/Volumes/Krieger/Users/zeraien/Development/ingager/results/env-ingager_results/lib/python2.7/site-packages/django/db/migrations/writer.py", line 410, in serialize
    "topics/migrations/#migration-serializing" % value
ValueError: Cannot serialize: <class django.db.models.fields.NOT_PROVIDED at 0x1076a7ae0>
There are some values Django cannot serialize into migration files.
For more, see https://docs.djangoproject.com/en/dev/topics/migrations/#migration-serializing

Possible duplicate of #733

Yes it certainly seems so.

closed as duplicate of #733


Enabling an easy version of the Clear-Host function

This has to be implemented differently once we support different hosts.
But for the sake of simplicity, I chose to implement it this way for now.
There is obviously no unit test as it's a UI-only thing with platform specific implementation, that we cannot test with out existing testing framework.
Fixes #382.

I'm glad that most of Pash is unit tested, but as you point out, no matter how vigilant we are, there will always be a handful of items that can't be tested that way.
What do you think of keeping a list, checked in to the repo? We can use it as a checklist/manual test plan before releasing, and as a TODO list of things to automate.

Yes, maybe that's a good attempt to keep track of these things.


Switch to GitHub Pages for hosting the documentation

As stated in the issue title, I'd like to propose moving the hosted documentation away from Read the Docs and using GitHub Pages instead for hosting. This was last discussed in https://github.com/PyWavelets/pywt/issues/706#issuecomment-1979049136 and, probably, a few times elsewhere.
Some of the advantages and reasons for this suggestion are as follows:

We receive greater control over the build process and we can modify it as we like, instead of having to configure extra build steps we might end up needing in a .readthedocs.yaml file
For enabling the rest of the interactive documentation for PyWavelets on latest versions, it is then possible to embed a custom Pyodide distribution, which seems to me should be the best approach for reusing the docs. I've previously tried a similar approach, but this new one that I propose should work better, since it would work without the need for nightly WASM wheels.
One less GitHub App to configure for this repository/organisation and fewer finicky permissions to handle.
and so on

Some things to be thought about:

PyWavelets is a package that has been present for almost nineteen years now, and a lot of links will get subjected to link rot if we don't preserve the style of the Read the Docs links, i.e., to link to the "stable" documentation and "latest" documentation under /en/stable/ and /en/latest/ respectively. Setting redirects for broken links is possible under the Read the Docs admin dashboard, but it's difficult to do the same thing on GitHub Pages.
How to best navigate "stable" and "latest" documentation updates on GitHub Pages. For the latter, it would be through a GitHub Actions job that gets triggered on pushes to the master branch and uses a fine-grained PAT to update the rebuilt docs in the gh-pages branch for a PyWavelets/docs repository
The features enabled via the Read the Docs add-ons will be lost. Not a big bummer, though, considering we host only the "latest" and "stable" versions and the version switcher has been the most useful one, IO. The version warning on an "unstable" version can be natively re-implemented using admonitions by customising the conf.py file.
and more things I might have missed at the time of writing this issue.

In principle I'm perfectly fine with migrating to GitHub Pages. We don't need the multi-version support that RTD provides, and we also don't need a latest/stable split but can always just deploy the latest dev version of the docs. New features are rare and will anyway be marked with a .. versionadded:: directive.
Don't worry about the redirects either, we can quite easily set those up even with URL rewriting that would (for example) drop the stable/ part of each link (I've done it for meson-python recently).

For enabling the rest of the interactive documentation for PyWavelets on latest versions, it is then possible to embed a custom Pyodide distribution, which seems to me should be the best approach for reusing the docs. I've previously tried a similar approach, but this new one that I propose should work better, since it would work without the need for nightly WASM wheels.

This is the key part, let's focus on that. I think it's a separate issue, one of the existing ones that deals with nightly wheels probably. I doubt we want to be in the business of hosting a whole distribution, since that doesn't scale very well. I'm still not 100% sure how the recent work by @Carreau et al. gets deployed to get us an up-to-date and working set of packages when loading JupyterLite inside the PyWavelets docs.

I'm also in favor of trying to find a solution that would favor nightly wheels instead of building a whole distribution; It in general better for the ecosystem as it's more flexible and reusable across projects. I'll try to investigate how this ties into JupyterLite.
I think we should also be able to build the wasm32 wheel on RTD as well if we don't want to go upload the wheel to the scientific Python nightly.

We're already uploading the nightly wheels to anaconda.org/scientific-python-nightly-wheels/pywavelets and don't plan to stop, so I think we're fine in that respect.

Oh, yeah, I missed that; then we shoudl just pull from there indeed.

Meh, I there is a bug in micorpip that actually mark the wasm32 wheels as incompatible...

Both of them are supposed to be the same platform actually – the rename from the Emscripten version to Pyodide + Year + build number in the platform tag was just to indicate that the built wheels are meant to work with the Pyodide distribution rather than purely wheels that are compiled with Emscripten/for WASM.

It might be a bug, micropip should accept both of them

I'll try to investigate how this ties into JupyterLite.
I think we should also be able to build the wasm32 wheel on RTD as well if we don't want to go upload the wheel to the scientific Python nightly.

With JupyterLite, the way forward would be that we use https://jupyterlite.readthedocs.io/en/stable/howto/pyodide/packages.html#installing-packages-at-runtime to install the wheels with a new piplite command (and maybe modify jupyterlite-sphinx to insert that as a cell automatically). But I think the neater way would be that we do build the wasm32 wheel with RTD (or switch to GitHub Pages like with this proposal), so that we have it installed beforehand (https://jupyterlite.readthedocs.io/en/stable/howto/pyodide/packages.html#bundling-additional-packages-by-default) since the issue to hide a particular cell in a notebook from execution (https://github.com/jupyterlite/jupyterlite/issues/508) isn't receiving much traction.
A custom Pyodide distribution with GitHub Pages would not scale very well, but should be fine for a package like PyWavelets.


Double space needed to "refresh" Ionide type checker

Describe the bug
Sometimes Ionide doesn't "refresh" itself when there are changes to the code e.g. intellisense or coloration isn't refreshed. I've seen that sometimes hitting two spaces (honestly!) will refresh the typechecker. Nothing else does it short of a reset, but for some reason two spaces does the trick.
Expected behaviour
The type checker should never get out of sync, but if it does, it's unclear why double-space refreshes it.
Machine info

Windows
.NET SDK version: 5 or 6
Ionide version: 5.9.0 but I've seen it in earlier versions for a while now.

I have same issue all the time. If I change something in one file and it affects the other, I have to edit anything in that other file, like hitting a space and backspace and then all the checking and what-else kicks in.

I have the same issue. Need to press space then delete the space to get syntex highlighting to kick in.

my guess based on these reports is that:

VScode opens the file
VSCode sends 'textdocument/opened' messages to the LSP
FSAC starts typechecking
VSCode sends highlighting/etc requests
those endpoints try waiting for a tiny bit for 'recent' typecheck responses
those endpoints stop waiting
FSAC finishes typechecking

a fix for this might be to force those endpoints to wait for fresh typechecking responses instead of trying to find recent ones


[WFCORE-6415] Upgrade Bouncy Castle from 1.73 to 1.74

Issue: https://issues.redhat.com/browse/WFCORE-6415
Diff: https://github.com/bcgit/bc-java/compare/r1rv73...r1rv74

Superseded by https://github.com/wildfly/wildfly-core/pull/5566


shell script with arguments

Are you requesting a feature or reporting a bug?
a feature
What is the current behavior?
I want to write a shell-script to use test cafe, and use it on npm script. But I need allow to developer, pass arguments to script, example
npm test

npm test -- --test 'lorem ipsum'

npm test -- --fixture 'lorem ipsum' --test 'lorem'

What is the expected behavior?
On npm scripts, if developer want to pass arguments from argv to process, they need to use double -- before all arguments

And the argv is passed automatically to process. I believe that dont be implemented yet on testcafe, giving many work to write a shell script with theses arguments
How would you reproduce the current behavior (if this is a bug)?
I add to package.json, script test calling my test.sh file.
In shell file, I want just call the testcafe like I neeed, e.g.
./node_modules/.bin/testcafe chrome \
 ./sources/angular/**/*.spec.js \
--app './node_modules/.bin/http-server public -s --push-state'

Hi Darlan,
At the moment I don't quite clear understand what the feature do you request. It seems you can do it with the current implementation.
I've tried two cases and they work properly.
Shell + npm command
package.json
"scripts": {
  "test": "testcafe chrome d:/tests"
},

shell
npm test -- -t "OK"
result
Only the test with the OK name is run
Shell + npm command + .sh file
test.sh
./node_modules/.bin/testcafe chrome d:/tests/number-id.js -r spec:./report.txt $0 $1 $2 $3
package.json
"scripts": {
  "test": "test.sh"
},

shell
npm test -- -t "OK"

I'm closing this since there were no activity here for a long time. Feel free to reopen the issue if it's still needed.
Also, you can try to run your tests on the latest TestCafe version.


BACKUP_FILEEXTENSIONANNOTATION and BACKUP_BACKUPCOMMANDANNOTATION are not passed to backup pod

the BACKUP_FILEEXTENSIONANNOTATION and BACKUP_BACKUPCOMMANDANNOTATION env variables are used to set the annotations on the PreBackupPods Pods created by wrestic, this  is great.
The problem is that these env variables are not passed into the backup pod itself, so wrestic is still searching for it's own defaults.
With https://github.com/vshn/k8up/pull/91 the defaults in k8up have changed to be k8up.syn.tools/* which is great, but they have not been updated in wrestic, this will be fixed with https://github.com/vshn/wrestic/pull/21. But in my understanding just changing them in k8up should be enough as they should be passed to the backup pod by k8up where they are then picked up by wrestic?

Hi @Schnitzel
I'm tracking this in the internal ticket: https://ticket.vshn.net/browse/APPU-2595
You're correct they should just be passed to the wrestic pods in order to get picked up, but unfortunately the operator doesn't do that yet.
It's planned to be implemented this or next week.

Fixed by https://github.com/vshn/k8up/pull/96


Add vterm-mode to evil-escape-excluded-major-modes

jk doesn't work as expected in vterm.
Do I need to also check for vterm feature flag?

Looks good to me. No need for the feature check. Thanks for the help!


removes unused ag-background-2 variable

At least, it appears to be unused, if I'm not mistaken.

thanks!


In Blazor- Using Tvalue for  tag to get the component instance in other page.

##Description
Is there any possibility of getting the instances of the component to another razor page using the Tvalue in  Tag.
For eg:-

Page 1
<CascadingValue TValue="test" />

Page 2
I need to get like the page instance like below.

this.test
Is this possible in blazor ?

I'm not sure why you're trying to specify TValue. You only need to use Value, e.g.:
<CascadingValue Value="test">...</CascadingValue>


Defining globals

I am working on a Appcelerator Titanium project, where the framework defines several globals that I would like to ignore.
Is there a suggested way to override them (through package.json for example) and keep using standard (instead of switching to eslint)?

From the README:
How do I ignore files?
The paths node_modules/, .git/, *.min.js, bundle.js, and coverage/ are automatically excluded
when looking for .js files to style check.
Sometimes you need to ignore additional folders or specific minfied files. To do that, add
a standard.ignore property to package.json:
"standard": {
  "ignore": [
    "**/out/**",
    "**/lib/select2/**",
    "**/lib/ckeditor/**"
  ]
}

@yoshuawuyts you probably misunderstood my question. I am trying to ignore certain globals from generating standard's errors through some config setting. But I finally settled on explicitly specifying
/* global Titanium, Allow, arguments */

in each file.

whoops, my bad.

Is there a resolution for this issue? I tend to work with APIs like ThreeJS, CocoonJS, PIXI, etc. which are often in global scope.

@mattdesl I put /* global foo */ at the top of all my files, it's the simplest thing I can think of. Other than to not use globals :)


Network sync - issue with server time in GMT

I seem to have an issue with the network time syncing, the time from google seems to be pulling down in US time rather than local time. I have never had this problem with the wittypi3 which uses the same code which is strange but anyway in case it helps, if I replace this line - https://github.com/uugear/Witty-Pi-4/blob/03b205ecb3df93db8c8fca35d9567951aef9d36d/Software/wittypi/utilities.sh#L142 with t=$(curl -sI --location http://google.com | grep '^Date:' | awk -F ': ' '{print $2}' | tr -d '\r' | sed -n '2p')
it seems to resolve the issue for me

I think it might be better to poll time.google.com rather than google.com. The time.google.com is a NTP server so correctly outputs GMT

On a fresh install the original date function provided in the code seems to work fine. I'm not sure what was wrong in my previous install

On a fresh install the original date function provided in the code seems to work fine. I'm not sure what was wrong in my previous install


Issue MBProgressHUD userInteractionEnabled

This code below set user interaction true, but disable user touch events. It seems that do inverted work. Is this correct?
The doc say:
    var userInteractionEnabled: Bool // default is YES. if set to NO, user events (touch, keys) are ignored and removed from the event queue.

    func startLoading() {
           let loading = MBProgressHUD.showHUDAddedTo(self.view, animated: true)
           loading.mode = MBProgressHUDMode.Indeterminate
           loading.labelText = Strings.Loading
           loading.userInteractionEnabled = true
    }

I have the same doubt...

Setting userInteractionEnabled = true means that the HUD receives touches. This in turn means that it prevents touches from passing through it to other views. Setting userInteractionEnabled = failse makes the hud opaque to touches, meaning that they pass through it to views that are positioned below it.


How to detect if animation ends

Describe your problem here.
I'm trying to change a character just when an animation ends, how do I do that? There's any property to use in getProperty?
Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
No

Thanks, I'll test it


degrees/radians

Currently radians are commented out: // skipping radian: rad = m / m
and degrees result in a primitive type losing type safety.
void foo(decltype(deg) a)
{}
void unitstest()
{
	foo(5 * rad);
}

This is because angles are not first-class citizens of the SI. The SI explanation for radians is that they're meters divided by meters (which is what the m / m part of the comment is supposed to mean). That would be a unitless value, which doesn't provide any type safety over its numerical type. The same goes for steradians.
I do see the advantage of having real units for them, but I don't want to deviate too much from the SI without good justification (or technical reasons). I'm willing to reconsider it if several people who deal with SI units that need angles want radians as first-class citizens.
I would suggest that you create your own degrees and radians and gradians if you need them, and add them your siunits.hpp or within their own unit system.

The problem is that with a type system that only knows about units, not about dimensions, it's impossible to distinguish between radians and dimensionless values, as both are unitless.
If you really need this functionality, you're probably better off using Boost.Units.

 It's so bad they even had to create a tool just for that.
In contrast this library is very appealing. Tiny and slick.
@zneak
Yeah I guess putting radians into its own system would make more sense.
Combining it with most SI units makes only limited sense anyway.
But I wonder how you could prevent/fix things like
decltype(deg) degrees = 5 * rad;
decltype(kg) kilograms = 5 * g;

The library is designed to allow it. You may want to take a look at example.cpp.
The only place it will matter is where you try to get the numerical value behind the quantity. To do so, you divide it by a unit. If you want degrees out of your degrees variable, you divide it by deg (and you'll get about 286.479). If you want radias, you divide it by rad (and you'll get about 5).

Ha indeed, thanks for pointing out the division "trick" (y)

@Trass3r Just as a note, I know how horrible it is to work with Boost, that is why I switched to this library (and then started contributing). When I wanted to add constexpr in a few places in Boost.Units, I was advised to do a full clone of all of Boost first, and a shallow recursive clone of all of it was the only alternative... Which took forever, but worked. Until btrfs balance segfaulted a few days after and took half my FS with it. Then I gave up :D
But enough with the rambling... There actually is some use in having rad as part of the SI system, as there are units derived from it (example). I'm still not sure whether it would make sense to do the same thing as Boost.Units here, though that won't change until I actually understand it... Did you have a look at it, @zneak?

Even within named units, lumens are defined as candela * steradians, so we're definitely missing out on not having angles (or solid angles, for that matter).
I'm not familiar with units that use them, so it's hard for me to tell if you could make it work by defining radians and steradians as base units. It seems to me that if you need to derive the angle from distance (or area) quantities, it wouldn't work to have radians/steradians declared as their own thing. But then again, if it's simply not how you use them, then maybe it'd work.
Practically, it's a two-line change to have radians as a base unit in siunits.hpp (three if you want degrees too). I'd love to have feedback from someone who knows that stuff better to decide if it's a good idea to have it in by default or not. I'll see if my physicist friends have an opinion on that matter.

@jplatte yes rad/s and rad/s² are the only useful combinations that came to my mind too and in fact the ones I intended to use in the first place.
Also I'm currently playing with 2 ideas:
// define decltype(unit) wrappers which prevent direct construction
struct Angle final : decltype(rad) { Angle(decltype(rad) o) : decltype(rad)(o) {} };
struct Force final : decltype(N) { Force(decltype(N) o) : decltype(N)(o) {} };
void foo(Angle angle, Force force)
{
	// Angle b(5); // error : no matching constructor
	printf("%f in deg\n", angle[deg]);
	printf("%f in kN\n", force[std::kilo() * N]); // a bit nicer than divide syntax
}

Just to not leave you hanging, my physicist friend said that people do use m/m to produce radians, so I'm really uneasy about adding radians as units. If that won't be your case, you're of course welcome to add them to your local siunits, which should be 3ish lines of code. That's what I'm the most comfortable with for now.
Maybe we could #ifdef angles as first-class units.


The font is invisible on my pc.

http://i.imgur.com/HJ4Ro69.png
I don't know hot to fix it. I even tried by making a custom style and using another font but even that didn't work or I did something wrong. Please help.
Thanks in advance!

Perhaps you could post the current custom style?
Did you try clearing the custom style text box? How about uninstalling and reinstalling the extension?

I have just found the reason. I once used a registery hack to hide all the caption text.
Link: https://www.youtube.com/watch?v=G1TC6KmlCCg
I undid that and your extension shows text again.
Now my question could I use a special custom style with another font so that I can use the registery hack and keep using your extension. Cause it seems weird to me that all text in the extension depends on the caption font.
Thanks,


Move PLI line and block comments to JS code

Required before removing PLI code which are strewn in the JS code as comments

Merged into 54 and master, closing


Python tiledbsoma SOMADataframe - create/write disagree on soma_rowid

SOMADataFrame create and write are inconsistent on whether soma_rowid is "accepted".

as expected, write requires it
but create will assert if the field is in the schema.
This makes it challenging to create and save a dataframe in one pass.  You have to drop the soma_rowid when calling create, and retain it when calling write.

it would be nice if they were consistent - which probably means that create allows this column as long as it is correctly typed.
In [1]: import pandas as pd

In [2]: import pyarrow as pa

In [3]: import tiledbsoma as soma

In [4]: soma_df = soma.SOMADataFrame("./foo")

In [5]: df = pd.DataFrame({'n_legs': [2, 4, 5, 100], 'animals': ["Flamingo", "Horse", "Brittle stars", "Centipede"]})

In [6]: soma_df.create(pa.Table.from_pandas(df).schema)

In [7]: for batch in pa.Table.from_pandas(df).to_batches(): soma_df.write(batch)
---------------------------------------------------------------------------
AssertionError                            Traceback (most recent call last)
Cell In [7], line 1
----> 1 for batch in pa.Table.from_pandas(df).to_batches(): soma_df.write(batch)

File ~/projects/TileDB-SOMA/apis/python/src/tiledbsoma/soma_dataframe.py:290, in SOMADataFrame.write(self, values)
    281 """
    282 Write an Arrow.RecordBatch to the persistent object.
    283
   (...)
    286 The ``values`` Arrow RecordBatch must contain a ``soma_rowid`` (uint64) column, indicating which rows are being written.
    287 """
    288 self._shape = None  # cache-invalidate
--> 290 assert ROWID in values.schema.names
    292 # TODO: contiguity check, and/or split into multiple contiguous writes
    293 # For now: just assert that these _already are_ contiguous and start with 0.
    294 rowids = [e.as_py() for e in values.column(ROWID)]

AssertionError:

In [8]: df['soma_rowid'] = df.index.astype(np.uint64)

In [9]: for batch in pa.Table.from_pandas(df).to_batches(): soma_df.write(batch)

In [10]: !rm -rf ./foo

In [11]: df
Out[11]:
   n_legs        animals  soma_rowid
0       2       Flamingo           0
1       4          Horse           1
2       5  Brittle stars           2
3     100      Centipede           3

In [12]: soma_df = soma.SOMADataFrame("./foo")

In [13]: soma_df.create(pa.Table.from_pandas(df).schema)
---------------------------------------------------------------------------
AssertionError                            Traceback (most recent call last)
Cell In [13], line 1
----> 1 soma_df.create(pa.Table.from_pandas(df).schema)

File ~/projects/TileDB-SOMA/apis/python/src/tiledbsoma/soma_dataframe.py:62, in SOMADataFrame.create(self, schema)
     55 def create(
     56     self,
     57     schema: pa.Schema,
     58 ) -> None:
     59     """
     60     :param schema: Arrow Schema defining the per-column schema. This schema must define all columns. The column name ``soma_rowid`` is reserved for the pseudo-column of the same name.  If the schema includes types unsupported by the SOMA implementation, an error will be raised.
     61     """
---> 62     assert ROWID not in schema.names
     64     self._create_empty(schema)
     65     self._is_indexed = False

AssertionError:

Fixed in #397


RPC method web3_sha3 not supported

Expected Behavior
We should support method web3_sha3 rpc.
https://github.com/ethereum/wiki/wiki/JSON-RPC#web3_sha3
Current Behavior
Now testrpc is not supported the web3_sha3.

Added to master. Will go out with the next release. Thanks!