Question: Efficiently shuffle array of fixed-width strings

Hello,
Along the lines of #4018 , if I want to shuffle a big array of fixed-width strings, should I just use np.random.permutation? Using numba-assisted function to shuffle the index (~30% faster) and then apply mask kills any speed gains and is even slower than just using numpy directly on strings. If I need to do around 10 million permutations, is there any way to speed it up more than what I currently have?

@numba.jit(nopython=True)
def permute_index_arr(index):
    return np.random.permutation(index)

repeat_times = [200_000,200_000,200_000]
arr = np.repeat(["AA", "BB", "CC"], repeat_times)

for i in range(1000):
    permuted = np.random.permutation(arr) # 67 iters/sec

index = np.arange(arr.shape[0])

# permuting only the index
for i in range(1000):
    permute_index_arr(index) # 88 iters/sec

for i in range(1000):
    permuted = arr[permute_index_arr(index)] # 56 iters/sec

I don't see a way to speed this up.  The results also seem to be pretty dependent on hardware, it seems.  On my laptop, I get 63 iters/sec, 110 iters/sec, and 86 iters per sec (using %timeit), so permuting the index and then gathering the results is 30% faster than permuting the string array directly for me.  However, you should go with your benchmarks since they reflect the hardware you have.
Numba is generally unlikely to provide much benefit when compiling single NumPy functions as our implementations are very similar to NumPy's.


Horizontal scrolling fix

This PR fixes a couple of issues:

Horizontal scrolling was broken, I managed to track it down to an incorrect style assignment (fixes #181)
A footer related test was failing, turned out to be another style assignment issue.

p.s. thanks for this component, it's by far the best table implementation I've found for bubbletea, and I'm using it extensively in my app!

Thanks for the fix! Glad it's helpful!


Handle façades for Dart code (native implementations of some functionality in dart)

Can you clarify what is needed, or a problem to repro?
Seems to me the facade layer is already in dart, so it just needs to be copied to the dist folder?

Yeah, but how is TS going to understand it, and compile the code correctly?
Do we need to write .d.ts files for this? Do we put the .js implementations
through TS? If so, how do we make sure we don't compile them to Dart?
Alex Eagle<EMAIL_ADDRESS>schrieb am Di., 24. März 2015 um
15:35 Uhr:

Can you clarify what is needed, or a problem to repro?
Seems to me the facade layer is already in dart, so it just needs to be
copied to the dist folder?
—
Reply to this email directly or view it on GitHub
https://github.com/angular/ts2dart/issues/85#issuecomment-85720485.

The resolution of this was having .dart files for platform specific façades, and have those shadow .ts files with the same name. This is implemented in the broccoli and gulp drivers for ts2dart.


Add serverless

https://github.com/serverless/serverless/blob/master/docs/telemetry.md#disabling-telemetry
to disable: set env var SLS_TELEMETRY_DISABLED=1
There is also undocumented SLS_TRACKING_DISABLED env var in code, which is mentioned in pr: https://github.com/serverless/serverless/pull/6867

To make opting out from tracking easier (in test runs) introduce SLS_TRACKING_DISABLED env variable

Closed via b0206b1


Angular 10

I am trying to update my website to angular 10, but apparently this component is not compatible with that version.

Hi @lauramgran,
The current package is compatible with Angular 8 for now. I will update the package to Angular 11. I am working on it for now and I push the new version of it till this weekend.
You can use the package after the new version released with Angular 10 and 11.

Its already updated?

The update will come tomorrow.

I have already been able to update the component, thank you very much!!


Allow escaping comma characters in CSV files.

Description
A CSV file can contain fields that contain comma characters. Such a file would be difficult to import as a table since comma is being used as a field delimiter. Note that is not specific to comma character, but can happen with any other delimiter character as well. This PR adds support for escaping delimiters that appear within CSV fields so that they don't get confused with actual delimiters.
Example CSV file with fields containing escaped comma delimiter:
id,name,json,ts
1,daffy duck,{"name":"daffy"\, "company":"linkedin"},0

Upgrade Notes
Does this PR prevent a zero down-time upgrade? (Assume upgrade order: Controller, Broker, Server, Minion)

[ ] Yes (Please label as backward-incompat, and complete the section below on Release Notes)

Does this PR fix a zero-downtime upgrade introduced earlier?

[ ] Yes (Please label this as backward-incompat, and complete the section below on Release Notes)

Does this PR otherwise need attention when creating release notes? Things to consider:

New configuration options
Deprecation of configurations
Signature changes to public methods/interfaces
New plugins added or old plugins removed

[ ] Yes (Please label this PR as release-notes and complete the section on Release Notes)

Release Notes
If you have tagged this as either backward-incompat or release-notes,
you MUST add text here that you would like to see appear in release notes of the
next release.
If you have a series of commits adding or enabling a feature, then
add this section only in final commit that marks the feature completed.
Refer to earlier release notes to see examples of text
Documentation
If you have introduced a new feature or configuration, please add it to the documentation as well.
See https://docs.pinot.apache.org/developers/developers-and-contributors/update-document

Codecov Report

Merging #6627 (50820bf) into master (1beaab5) will decrease coverage by 22.52%.
The diff coverage is 42.85%.

@@             Coverage Diff             @@
##           master    #6627       +/-   ##
===========================================
- Coverage   66.44%   43.92%   -22.53%
===========================================
  Files        1075     1358      +283
  Lines       54773    66505    +11732
  Branches     8168     9694     +1526
===========================================
- Hits        36396    29210     -7186
- Misses      15700    34829    +19129
+ Partials     2677     2466      -211

Flag
Coverage Δ

integration
43.92% <42.85%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...ot/broker/broker/AllowAllAccessControlFactory.java
100.00% <ø> (ø)

...t/broker/broker/BasicAuthAccessControlFactory.java
0.00% <0.00%> (ø)

.../helix/BrokerUserDefinedMessageHandlerFactory.java
52.83% <0.00%> (-13.84%)
:arrow_down:

...org/apache/pinot/broker/queryquota/HitCounter.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...che/pinot/broker/queryquota/MaxHitRateTracker.java
0.00% <0.00%> (ø)

...ache/pinot/broker/queryquota/QueryQuotaEntity.java
0.00% <0.00%> (-50.00%)
:arrow_down:

...ker/routing/instanceselector/InstanceSelector.java
100.00% <ø> (ø)

...ceselector/StrictReplicaGroupInstanceSelector.java
0.00% <0.00%> (ø)

...roker/routing/segmentpruner/TimeSegmentPruner.java
0.00% <0.00%> (ø)

...roker/routing/segmentpruner/interval/Interval.java
0.00% <0.00%> (ø)

... and 1374 more

Continue to review full report at Codecov.

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


fix bitrate overflow issue when adaptive quality turns on

reviewed at:https://rbcommons.com/s/OpenH264/r/1577/

pls avoid putting error-CI commit history in pull requests


Sort variants by sig

Sorting reviewed variants in gene left side variant pannel by significance.  This PR corresponds to the following issue on the clin.iobio project board:
https://github.com/iobio/clin.iobio/issues/141

quarantest build successful. Demo link at
http://339ed46e.quarantest.iobio.io


Update example releaseDirectory

The release directory should be build/app/outputs/apk/release not app/build/outputs/apk/release

This can really depend on your build and development setup. I believe that default Android Studio projects output their assembleRelease task to app/build/outputs/apk/release.


fix(network): workaround to cancel outstanding buffering network requests

So weird 🙈 thank you so much for figuring this out 🙏


Execute last command

It would be great to be able to execute the last command.

v0.5.0

The last executed command is now stored and can be executed again via qc exec --last
(for #9)

v0.5.1

The last selected command is now only stored when there actually was a command selected and
the dialog wasn't quit without selecting a command (for #9)


Missing or invisible help text

Trying to use SystemUI tuner on an Android 13 tablet. The help screens are less than useful.

Ok new year and come Pesach


"Bira", "Negrești" and "Rediu" are listed in the drop-down

Description:
"Bira", "Negrești" and "Rediu" are listed in the drop-down menu alongside its corresponding county and commune, according to the law
Precondition:
The website is up an running.

Step 1
Type "Bira" in the search bar.

Expected results
The location is listed in the drop-down menu as "Sat Bira, NEAMȚ (Bira)" and "Comuna Bira, NEAMȚ".

Step 2
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 3
Type "Negrești" in the search bar.

Expected results
The location is listed in the drop-down menu as "Sat Negrești, NEAMȚ (Bira)".

Step 4
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 5
Type "Rediu" in the search bar.

Expected results
The location is listed in the drop-down menu as "Sat Rediu, NEAMȚ (Bira)".


Frame script

Some bug fixes to get icycle further.

@tobytailor are the changes here still relevant?


STORM-2632: Apply new code style to storm-sql-kafka

Reduce the max allowed violation count to 0.

+1


Overfit 1D Conv Model on Single Sample

loss of 1000 variational autoencoder and it seems that it is worse than 2d-conv


fix: add missing middleware package

Add the missing @lido-nextjs/middleware package to the "dependencies" section of the package.json file.
The MiddlewareService symbol from this package is used in the src/common/consensus-provider/consensus-fetch.service.ts file but was not explicitly listed in dependencies. Now it is fixed.

If I understand correctly, this package should additionally be added to the "peerDependencies" in the fetch package. to avoid such problems in the future

If I understand correctly, this package should additionally be added to the "peerDependencies" in the fetch package. to avoid such problems in the future

I don't think that we should add @lido-nextjs/middleware to "peerDependencies" of the @lido-nestjs/fetch package because this package is not required. Using the fetcher in middleware is only one of the possible techniques of how the fetcher can be used. It is possible to use the fetcher without defining the middleware.
@eddort please, let me know if you disagree.


raidboss: Ultima EX timeline and minimal triggers

Ultima is a mostly-typical ARR-style encounter. It consists of four phases each with its own rotation, with each activating in turn at HP thresholds. Phases 1/2/4 are reasonably well-behaved and presented basically no problems working out. Phase 3 appears to be incredibly convoluted almost beyond belief.
Triggers first though. As is normal for ARR-era encounters, the vast majority of Ultima's abilities have no cast times. This means most of our triggers will have to be timeline-driven. This is mostly not an issue, but we will discuss the exceptions later. For now, the major important triggers are in place. (Raidwide, tank swap, and off-tank cleave.)
The major issue experienced with generating this timeline was in phase 3. At 64.9% HP, Ultima enters its Ifrit phase, where it (mostly) alternates ability blocks centered on Eruption or Crimson Cyclone. Most of the ridiculousness is noted in-line in the comments, but it is astonishing how much variability Square seems to have put into what is likely the shortest of the phases! I haven't yet been able to fully test whether this variability is fully random or whether it might be some HP-based thresholds within the phase. (Unfortunately it can take 2-3 minutes of waiting around within phase 3 t o see whether Ultima does something or not, so it's not easy to test.)
Phase 4 also deserves a mention. It looks like this encounter uses 21 log lines instead of 27 for the Aetheroplasm headmarkers in phase 4. (I'll be adding those into the PR, both timeline and triggers, once maintenance is over and I can test them.) This would fit in with the lack of 27 log lines in other ARR-era content.
The transition to phase 4 is indicated by the first cast of Aetheric Boom, and the rotation starts fresh from there. None of the Aetheric Boom casts appear to delay the timeline by more than a few seconds. The appearance of the Ultima Bits similarly causes no delay. The gunship crashes, inflicting proximity damage with Freefire, seem to interrupt the rotation and postpone whatever they interrupted by about 12 seconds. All this is to say, we need to sync phase 4 much more aggressively than we normally would. Fortunately Tank Purge occurs only once per rotation, so we do have an if-all-else-fails stopgap.
Finally, Homing Lasers needs special mention. There's a point in the phase 3 rotation at 732 where a shorter "bridge" block between two standard ability blocks is indicated by a Homing Lasers usage. Unfortunately, we will have no way to definitively warn the player if and only if Homing Lasers is used here. I think we'll just have to accept the possibility of a phantom tank cleave callout here and hope for the best.
Realistically, most groups should clear phase 3 long before any of this becomes a problem, but we do need to do our best because of how timeline-dependent the trigger set is.

Are there other triggers you think should be added here? (Or should we merge this first and then add more?)
Mostly thinking of:
- are there phase 1 in/out things?
- aetheric boom (at least maybe "pop orbs (some word describing the pattern)"?)
- freefire places to run or maybe it's obvious from the ground and we can skip it?

I think it's mostly there, yes. You hit on the major ones already, the only other one I would probably add is a warning for "You have been targeted by a homing Aetheroplasm", which I still have to add/test.
Aetheric Boom, yes, you're right, we should add a Boom counter and notify which it is based on that. Should be simple enough. Freefire is the standard proximity markers, and we haven't been completely consistent with whether or not we call those. Ordinarily I would say we shouldn't bother, but given that the modern convention is to call stuff and let the user mute it if needed, it might be better to see whether there's consistency in the locations.
I'll be adding some trigger updates later, but unfortunately I've run into a configuration issue of some sort that's making the test suite fail any new trigger additions. Once I get that worked out I'll send in some trigger updates.

Okay, this is untested in-game since I had a surprise mount farm tonight, but I think this is close to the final trigger set at least. I wasn't able to find any data on where the Freefire proximity AoEs come from, since the Assault Craft that actually cast thoseare spawned at the start, and there aren't any startsUsing lines. I haven't mathed out whether Freefire comes at a set time after Booms, or whether it's on a separate HP threshold, but I can look for that.
Other than that, I think it's Good Enough. There will inevitably be minor tweaks to the phase 3 timeline, but it should function for 90% of what people need.


Release v0.3.0 / Re-export num_traits::{One, Zero} from ark-std

Description
This PR re-exports num_traits::{One, Zero} from ark-std as well as prepares this repo for a release to crates.io.

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

[x] Targeted PR against correct branch (master)
[x] Added a relevant changelog entry to the Pending section in CHANGELOG.md
[x] Re-reviewed Files changed in the Github PR explorer

N/A:

[ ] Linked to Github issue with discussion and accepted design OR have an explanation in the PR that describes this work.
[ ] Wrote unit tests
[ ] Updated relevant documentation in the code

It passes the checks, but let us be careful with this one (it is too important!).
If this PR looks good and is ready, one with write permission can (1) merge it and (2) add a GitHub tagged release.

(I don't have write access and would need someone with it to merge and also do cargo release)


Script for preparing calibration and test sets

Related issue is #108. Previous related (unmerged) PR is https://github.com/mlcommons/mobile_app_open/pull/123.
The script prepares and outputs the test sets to output/mlperf_datasets folder, which can directly be copied to a device for accuracy evaluation (excludes any ground truth files). I've used the processing scripts provided by MLPerf.
Calibration sets are in output/calibration_set folder.
Calibration images (except for SQuAD) are not processed. Submitters may need to further preprocess calibration data for compatibility with their SDKs.

We will need to work around web proxy as I had done using chunk downloads:
Fetching COCO val2014.zip
% Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
Dload  Upload   Total   Spent    Left  Speed
8 6337M    8  536M    0     0   351k      0  5:07:17  0:26:00  4:41:17  120k
12 6337M   12  811M    0     0   353k      0  5:06:00  0:39:10  4:26:50  105k
curl: (18) transfer closed with<PHONE_NUMBER> bytes remaining to read

@d-uzlov  Not sure why the code format check is failing. In the logs I see the following, but running clang-format on these files makes no changes:
/var/lib/jenkins/workspace/mobile_app_open/PullRequest-CodeFormattingCheck:/home/mlperf/mobile_app -w /home/mlperf/mobile_app -u 109:114 mlcommons/mlperf_mobile:1.0 android/formatters/run-format-code.sh
Updated/new C++ files: android/cpp/backends/external.cc android/cpp/utils.cc flutter/cpp/backend.h flutter/cpp/backends/external.cc flutter/cpp/backends/external.h flutter/cpp/binary/main.cc flutter/cpp/c/backend_c.h flutter/cpp/c/type.h flutter/cpp/dataset.h flutter/cpp/datasets/ade20k.cc flutter/cpp/datasets/ade20k.h flutter/cpp/datasets/allocator.cc flutter/cpp/datasets/allocator.h flutter/cpp/datasets/coco.cc flutter/cpp/datasets/coco.h flutter/cpp/datasets/imagenet.cc flutter/cpp/datasets/imagenet.h flutter/cpp/datasets/squad.cc flutter/cpp/datasets/squad.h flutter/cpp/datasets/squad_utils/common.h flutter/cpp/datasets/squad_utils/tfrecord_reader.h flutter/cpp/datasets/squad_utils/types.h flutter/cpp/flutter/dart_backend_match.cc flutter/cpp/flutter/dart_mlperf_config.cc flutter/cpp/flutter/main.cc flutter/cpp/flutter/main.h flutter/cpp/mlperf_driver.cc flutter/cpp/mlperf_driver.h flutter/cpp/proto/test.cc flutter/cpp/utils.cc flutter/cpp/utils.h flutter/cpp/utils_test.cc
No such file or directory
No such file or directory
No such file or directory
No such file or directory
No such file or directory
No such file or directory
No such file or directory
No such file or directory
No such file or directory
No such file or directory
No such file or directory
No such file or directory
No such file or directory
No such file or directory
No such file or directory
No such file or directory
No such file or directory
No such file or directory
No such file or directory
No such file or directory
No such file or directory
No such file or directory
No such file or directory
No such file or directory
No such file or directory
No such file or directory
Build step 'Run with timeout' marked build as failure
Archiving artifacts
Setting status of c5793469e429d843d42faa781c37befd02f0239c to FAILURE with url https://mlperf.xored.com/job/mobile_app_open/job/PullRequest-CodeFormattingCheck/127/ and message: 'Failed
'
Using context: Code formatting
Finished: FAILURE

Running the formatting script in prep-datasets branch doesn't format anything, but if I merge it into the master branch I do get the exact same error.
Seems like our formatting script tries to format files deleted in the previous PRs, and fails. We should probably fix it later.
@fatihcakirs can you rebase you branch to the last commit in the master branch?

@fatihcakirs and @d-uzlov OK if I merge this?

@mcharleb can we add some documentation to the /datasets folder?
If we already have one elsewhere, can you at least create a /datasets/readme file with a link to the main documentation?
Oh, and  I guess you forgot to update the Folder Structure section of the repo readme.

Thank you @d-uzlov and @mcharleb , I've added a brief description to the Folder Structure section in the repo readme. This should suffice in my opinion, the make file is itself self-explanatory. Unless you need a more detailed readme file in the datasets folder, I'm fine with the merge.


Update the reset timer

In this update, I merged the setTimeout in with the current seconds so it should use a bit more CPU then before because it's basically calculating every seconds twice as much. However, you shouldn't see too much of a difference.
In this update I added the feature where the server will not reset unless if the bot average mass is less than 100, so no more worrying that your 500 mass bot will die because of a server reset and you getting no XP :3
I'll have the clean the code a crap ton to help release mb's of ram, but for now this is great!

I just read over the code again and looks pretty efficient now to me :+1:

why are you updating the version in 2 places? why not just include the version file in lvlgen?

@moerderin When people download the file, it checked the version at the version file on Github.

Tested it out already, works pretty well :)

Nice improvements! :)

How can we use this @Cr4xy  @MastaCoder

@NoorAgario There is an option in the config.js to change the minutes for the restart.

should I download the whole Agar-lvlgenerator again ? @MastaCoder

Yeah @NoorAgario


33 pre commit changes

This PR:

contains one manual change to the .pre-commit-config.yaml
updates the secrets file (automatically done by pre-commit)
cleans up repo files using pre-commit (automatically done by pre-commit)

The pre-commit CI is failing because it requires some additional configuration. This is addressed in https://github.com/button-inc/digital_marketplace/pull/29. If preferred, I can turn off this action temporarily.

@BCerki I think you mentioned on chat that you'll fix pre-commit.ci as part of this PR, yes? https://github.com/button-inc/digital_marketplace/pull/13#discussion_r761509752

Perfect, thanks! That helps with the review :)

I'd merge #32 first, if possible. There might be conflict in .eslintrc.js as both PRs touch L24. But maybe we'll git lucky ;)

@wenzowski, I did get a merge conflict on this. I resolved it in the online editor, but it looks like that killed your approving review

For other reviewers, this is easier to make sense of using git diff -w to ignore insignificant whitespace changes than using the github gui.


Use new HashMap implementation in the TextServer and Font.

Depends on #60881.

It's not much data, but so far it seems to be substantially slower than the old implementations - I was checking #59028, and shaping large pages takes almost 5 time longer with the new HashMap2 than it was with the old HashMap + Map.

Thanks!


update ratio for new content

updated the image in https://github.com/istio/istio/pull/6063
this matches the new one

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: ldemailly
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: geeknoid
Assign the PR to them by writing /assign @geeknoid in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@geeknoid should I redo it for master or you will propagate ?

I'm doing bi-directional merging, so no worries.
On Thu, Jun 7, 2018 at 8:05 AM Laurent Demailly<EMAIL_ADDRESS>wrote:

@geeknoid https://github.com/geeknoid should I redo it for master or
you will propagate ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio.github.io/pull/1463#issuecomment-395454465,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AVucHbeEjJqO2jVbU9m7aCtBevFXMx5Tks5t6UEegaJpZM4Udm6z
.

cool, thanks


Not working in iOS14

Unable to use the widget with iOS 14. Getting below error
════════ Exception caught by rendering library ═════════════════════════════════════════════════════
The following assertion was thrown during performLayout():
'package:flutter/src/widgets/scroll_position.dart': Failed assertion: line 582 pos 12: '_pendingDimensions': is not true.
Either the assertion indicates an error in the framework itself, or we should provide substantially more information in this error message to help you determine and fix the underlying cause.
In either case, please report this assertion by filing a bug on GitHub:
https://github.com/flutter/flutter/issues/new?template=BUG.md
The relevant error-causing widget was:
SmartRefresher file:///XXX/XXX/XXX/XXX/XXX/lib/Components/PostWidget.dart:82:15
When the exception was thrown, this was the stack:
#2      ScrollPosition.applyNewDimensions (package:flutter/src/widgets/scroll_position.dart:582:12)
#3      ScrollPositionWithSingleContext.applyNewDimensions (package:flutter/src/widgets/scroll_position_with_single_context.dart:108:11)
#4      RenderSliverRefresh.performLayout (package:pull_to_refresh/src/internals/slivers.dart:189:39)
#5      RenderObject.layout (package:flutter/src/rendering/object.dart:1777:7)
#6      RenderSliverRefresh.layout (package:pull_to_refresh/src/internals/slivers.dart:152:13)
...
 Not just related to iOS

I/flutter (26207): ══╡ EXCEPTION CAUGHT BY RENDERING LIBRARY ╞═════════════════════════════════════════════════════════
I/flutter (26207): The following assertion was thrown during performLayout():
I/flutter (26207): 'package:flutter/src/widgets/scroll_position.dart': Failed assertion: line 582 pos 12:
I/flutter (26207): '_pendingDimensions': is not true.
I/flutter (26207):
I/flutter (26207): Either the assertion indicates an error in the framework itself, or we should provide substantially
I/flutter (26207): more information in this error message to help you determine and fix the underlying cause.
I/flutter (26207): In either case, please report this assertion by filing a bug on GitHub:
I/flutter (26207):   https://github.com/flutter/flutter/issues/new?template=BUG.md
I/flutter (26207):
I/flutter (26207): The relevant error-causing widget was:
I/flutter (26207):   SliverRefresh
I/flutter (26207):   file:///home/xxx/.pub-cache/hosted/pub.dartlang.org/pull_to_refresh-1.6.1/lib/src/internals/indicator_wrap.dart:315:12
I/flutter (26207):
I/flutter (26207): When the exception was thrown, this was the stack:
I/flutter (26207): #2      ScrollPosition.applyNewDimensions (package:flutter/src/widgets/scroll_position.dart:582:12)
I/flutter (26207): #3      ScrollPositionWithSingleContext.applyNewDimensions (package:flutter/src/widgets/scroll_position_with_single_context.dart:108:11)
I/flutter (26207): #4      RenderSliverRefresh.performLayout (package:pull_to_refresh/src/internals/slivers.dart:189:39)
I/flutter (26207): #5      RenderObject.layout (package:flutter/src/rendering/object.dart:1777:7)
I/flutter (26207): #6      RenderSliverRefresh.layout (package:pull_to_refresh/src/internals/slivers.dart:147:13)
I/flutter (26207): #7      RenderViewportBase.layoutChildSequence (package:flutter/src/rendering/viewport.dart:507:13)
I/flutter (26207): #8      RenderViewport._attemptLayout (package:flutter/src/rendering/viewport.dart:1561:12)
I/flutter (26207): #9      RenderViewport.performLayout (package:flutter/src/rendering/viewport.dart:1470:20)
I/flutter (26207): #10     RenderObject._layoutWithoutResize (package:flutter/src/rendering/object.dart:1634:7)
I/flutter (26207): #11     PipelineOwner.flushLayout (package:flutter/src/rendering/object.dart:884:18)
I/flutter (26207): #12     RendererBinding.drawFrame (package:flutter/src/rendering/binding.dart:436:19)
I/flutter (26207): #13     WidgetsBinding.drawFrame (package:flutter/src/widgets/binding.dart:914:13)
I/flutter (26207): #14     SchedulerBinding._invokeFrameCallback (package:flutter/src/scheduler/binding.dart:1117:15)
I/flutter (26207): #15     SchedulerBinding.handleDrawFrame (package:flutter/src/scheduler/binding.dart:1055:9)
I/flutter (26207): #19     _invoke (dart:ui/hooks.dart:251:10)
I/flutter (26207): #20     _drawFrame (dart:ui/hooks.dart:209:3)
I/flutter (26207): (elided 5 frames from class _AssertionError and dart:async)

flutter doctor:
[✓] Flutter (Channel beta, 1.22.0-12.1.pre, on Linux, locale en_GB.UTF-8)
    • Flutter version 1.22.0-12.1.pre at /home/xxx/development/flutter
    • Framework revision 8b3760638a (5 days ago), 2020-09-15 17:47:13 -0700
    • Engine revision 4654fc6cf6
    • Dart version 2.10.0 (build 2.10.0-110.3.beta)

Sorry, it is working but the refresh icon just kicks in once you've pulled down a bit.

Try 1.6.2,If it work,please tell me.I ａｍ going to closeit

Working now. Thanks for the fast changes!

I'll add, I've not testing on iOS 14, just Flutter beta on Android as the same issue was happening there. You need beta to deploy to an iOS 14 device properly at the moment:

Upgrading to Flutter 1.22 beta allows you to build, test, and deploy to iOS without issue. Upgrading to 1.20.4 stable allows you to build and deploy to iOS 14, but not debug.

https://flutter.dev/docs/development/ios-14#launching-flutter-with-flutter-tools
so probably fixed on iOS 14. I'll be testing that later this week.


Fix URL links

I fixed the links from the bash commands:

az-ad-sp-create-for-rbac
az-account-show

@vmsilvamolina : Thanks for your contribution! The author, @iainfoulds, has been notified to review your proposed change.

Thanks, @vmsilvamolina. These changes are good to merge.
#sign-off


tableName from the Language Model

I can´t customise the tableName from this Model =>
https://github.com/lajax/yii2-translate-manager/blob/master/models/Language.php#L58

You can customise the name of the table by changing the languageTable public variable.
eg.:
'translatemanager' => [
            'class' => 'lajax\translatemanager\Module',
            'languageTable' => 'YourTableName',
            // ...
    ]

Best Regards,
Lajax

Thank You. :+1:


Missing info

You do not specify what to "import" to get the examples working. No need to be so secretive about it!
Also, a complete code example would be helpfull.

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 6eacc65c-8d34-8fd6-cf1f-98ac3ed7ebd1
Version Independent ID: 9d6d5c4e-8e9d-8646-4ec9-c2877d0fbd9f
Content: Azure Azure Digital Twins Core client library for Python
Content Source: docs-ref-services/latest/digitaltwins-core-readme.md
Service: digitaltwins
GitHub Login: @johngallardo
Microsoft Alias: jgalla

@adankert70 Apologies for the late reply. Thanks for reaching out to us and reporting this issue. We are looking into this issue and we will provide an update.


Update to alex 9

Doesn't look like the major Alex version change is what is causing the Alex linting step to hang. CC @yob
But the combo of latest alpine and latest Alex might be?

oh javascript :disappointed:

Yeah, it was a bit of a throw stuff at the wall scenario. :-p


arguments fault when numArg of a function is more than 2

Description of the issue
i build a function called Transfer with 4 args. but when i invoke the function, arguments' values in function are not the same as the input variables.
Type (put an x sign in the square brackets)

[x] bug report
[ ] feature request
[ ] Documentation improvement

Checklist

[x] Running latest version of code.
[x] This issue has not been reported earlier.

Your environment

OS: ubuntu
Go version:1.10.2
Release tag/commit of the code: master: 13b9dfa70af55896334ea02de3b5a05ec6dc4eee

Expected behaviour
successlly transfer from fromHash to toHash with the amount
Actual behaviour
got wrong arguments
Steps to reproduce

i write a contract named ICOTemplate.go, here: https://github.com/KickSeason/go-smart-contract-workshop/blob/dev/ICOTemplate/ICOTemplate.go
i set up neo-privetnet using docker and neo-python using source code
compile contract using:
neo-storm compile -i ICOTemplate.go
then i use neo-python deploy it and invoke deploy and balanceOf successfully
problem happened when invoke transfer. you can see i write runtime.Notify at line 84-86 and line 150-153 of ICOTemplate.go to compare variables and args i got. but got different values.

before call transfer:
			runtime.Notify(args)
			fromHash := args[0].([]byte)
			toHash := args[1].([]byte)
			amount := args[2].(int)
			runtime.Notify(fromHash)
			runtime.Notify(toHash)
			runtime.Notify(amount)
			return I.Transfer(ctx, fromHash, toHash, amount)

during transfer:
func (I ICOSettings) Transfer(ctx storage.Context, fromHash []byte, toHash []byte, amount int) bool {
	runtime.Notify("transfer")
	runtime.Notify(fromHash)
	runtime.Notify(toHash)
	runtime.Notify(amount)

output:

toHash became InteropInterface
amount disappears
Any extra info ( for eg. code snippet to reproduce, logs, etc. )

I think I make the stack full and cant push into more variables.
So when I try getting the arg, I got the method receiver not the argument.
I use function instead of method to avoid the problem now.

@KickSeason Hello! I've also run into similar problem and made a fix which worked for myself.
https://github.com/CityOfZion/neo-storm/pull/51
There are, probably, more cases to consider there. Does always work as expected when you use function instead of method?


workflows: fix yaml syntax error

whitespace sensitivity :(

"The directory you're trying to deploy named /home/runner/work/jspecify/jspecify/docs/build doesn't exist. Please double check the path and any prerequisite build scripts and try again."
Also some deprecation warnings, which may stand some chance of biting us someday.
Thanks again for fighting all this....

We're making progress as we can see the files are at least downloaded to the image.


[SPARK-19606][MESOS] Support constraints in spark-dispatcher

What changes were proposed in this pull request?
A discussed in SPARK-19606, the addition of a new config property named "spark.mesos.constraints.driver" for constraining drivers running on a Mesos cluster
How was this patch tested?
Corresponding unit test added also tested locally on a Mesos cluster
Please review http://spark.apache.org/contributing.html before opening a pull request.

Can one of the admins verify this patch?

test this please

Test build #82937 has started for PR 19543 at commit 11d5859.

Test build #82937 has finished for PR 19543 at commit 11d5859.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/82937/
Test FAILed.

Merged build finished. Test FAILed.

@felixcheung - fixed scala-style issues and also updated the docs to include the new property

Jenkins, retest this please

Test build #82946 has started for PR 19543 at commit efdc09c.

Test build #82946 has finished for PR 19543 at commit efdc09c.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/82946/
Test FAILed.

My apologies. Reread the docs and ran style checks locally this time. Fingers crossed

Jenkins, retest this please

Test build #82963 has started for PR 19543 at commit c587946.

Test build #82963 has finished for PR 19543 at commit c587946.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/82963/
Test PASSed.

@susanxhuynh would you like to review?
also looks like @ArtRand has some comments

@ArtRand - thanks for the feedback. I made the suggested changes to the docs and added some more tests - including a test w/ multiple constraints

Just one super-nit.

LGTM.

which release version is this intended for ?

@ttashi-rms v2.2 and up

@felixcheung - any chance of getting this merged into the upcoming 2.2.1 release? I cleaned up the merge conflict

@susanxhuynh or anyone from the mesos side would you please review?

@pmackles your changes works great. we had to update SJS (spark-job-server) side to support the new param for dispatcher. Ended up updating the manager_start.sh incase anyone is trying to figure it out.

@susanxhuynh, @ttashi-rms, @ArtRand - thanks for the feedback. I was able to make all of the suggested changes.

add to white list

Jenkins, retest this please

Test build #83718 has started for PR 19543 at commit 158b6b9.

Test build #83718 has finished for PR 19543 at commit 158b6b9.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/83718/
Test PASSed.

@susanxhuynh, @ttashi-rms, @ArtRand please take a look

LGTM

thanks @susanxhuynh
merged this to master.
the cherry pick to 2.2 was non-trivial, but merged, please keep an eye for this and please help test 2.2.1!


7672 create pipeline for gold cluster

Added pipelines for deploying rtrans builds to gold and gold dr environments:

feature-build
release
deploy

Reviewed and tested, all is good.


[Network]: _initializeInternalChannel: Unable to initialize channel. Attempted to contact 1 Peers. Last error was Error: 2 UNKNOWN: access denied: channel [mychannel] creator org [Org1MSP]

Following the instructions in the README leads to this error when loading a UI in the browser.

Node v10.15.0
OSX Mojave 10.14.5
VSCode 1.35.0
docker-compose version 1.24.0, build 0aa5906
Docker version 18.09.2, build 6247962
go1.12.5 darwin/amd64

same issue here
kindly advise

The reason is what the identity of CA node and key files are needed on your local environment. I added how to do that on README.md and now pull requesting, please wait a moment to merge.
You can check this operation on my repo folked;
https://github.com/taijihagino/global-financing-blockchain/tree/develop

has been merged:)

I am running into this problem with a live, default IBM Cloud Blockchain V2 cluster.    Registering Admin & wallet works, but executing a transaction fails with these messages.
I noted that registering an Admin always works, even when I clobber the PEM string.

@world2mark A few code changes would be needed to run this example on IBM Blockchain Platform V2. Try using the code and instructions on this repo instead - https://github.com/IBM/Global-Finance-on-Blockchain

@world2mark - was your problem resolved?

Thanks for the reply; I'm still in development and will update the forum
with my results.
Mark!
On Wed, Oct 9, 2019 at 12:50 PM ljbennett62<EMAIL_ADDRESS>wrote:

@world2mark https://github.com/world2mark - was your problem resolved?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/IBM/global-financing-blockchain/issues/9?email_source=notifications&email_token=AJISEGMZ62NYKSCF2ILC2NTQNYDW7A5CNFSM4HWQA7NKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAYRS5Y#issuecomment-540088695,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJISEGPV2IBV3KKFIBQUJA3QNYDW7ANCNFSM4HWQA7NA
.


Log dataflow messages at appropriate levels

The Python Dataflow Runner previously logged every message received at INFO by default, only storing the most recent error message to return once a pipeline reached a failed state. This leaves that mechanism in place, but logs messages with their corresponding importance (DEBUG, INFO, WARNING, ERROR) as they're received as well. This should surface errors more clearly in logs after jobs exit.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

Run PythonDocs PreCommit

Run Python_Integration PreCommit

LGTM


Address SettingSelector.Any

Per API Review (https://apiview.azurewebsites.net/Assemblies/Review/4f563eae75b14e4e8dea2a632e096f82)
Resolve name of SettingSelector.Any.

Per discussion with @KrzysztofCwalina, we will not change the naming here.


Support Lights

Hella supplies two types of lights:

BASIC_LIGHT
DIMMABLE_LIGHT

None of these is supported due to the lack of a testing device on my (@muhlba91) end.
The corresponding Home Assistant entity is the Light Entity.
The API description by Hella for lights can be found here: https://github.com/hella-info/onyx_api#lights.

@clostermannshof would you mind posting the response of one of your dimmable lights using the /devices/xyz endpoint?
the following scenarios would be awesome to see:

light turned off
light tuned to 50%
light turned on
this allows me to see the expected states and how they vary from state to state.

additionally, if possible the /events endpoint would be very useful as well for the following example:

set the light off
start querying the endpoint
dim the light from 0 to y%
set the light to off
set the light to on
this allows me to see what updates are expected to be received when actions are happening to the light.

For simplicity, I am sending all the data for one of three LEDs with the name "Licht links" and in our case /devices/21e6048b-adf1-41b0-833f-82452cdc5fad
for light turned off:
{
    "name": "Licht links",
    "type": "dimmable_light",
    "actions": ["light_off", "light_on", "stop", "wink"],
    "properties": {
        "actual_brightness": {
            "type": "numeric",
            "minimum": 0,
            "maximum": 65535,
            "value": 0,
            "readonly": true
        },
        "dim_duration": {
            "type": "numeric",
            "minimum": 20,
            "maximum": 3600000,
            "value": 5000,
            "readonly": false
        },
        "target_brightness": {
            "type": "numeric",
            "minimum": 0,
            "maximum": 65535,
            "value": 0,
            "readonly": false
        }
    }
}

for light turned to 50% (you can't get exactly 50% via the app as you can only slide a tile without an info about the percentage):
{
    "name": "Licht links",
    "type": "dimmable_light",
    "actions": ["light_off", "light_on", "stop", "wink"],
    "properties": {
        "actual_brightness": {
            "type": "numeric",
            "minimum": 0,
            "maximum": 65535,
            "value": 33153,
            "readonly": true
        },
        "dim_duration": {
            "type": "numeric",
            "minimum": 20,
            "maximum": 3600000,
            "value": 6000,
            "readonly": false
        },
        "target_brightness": {
            "type": "numeric",
            "minimum": 0,
            "maximum": 65535,
            "value": 33153,
            "readonly": false
        }
    }
}

for light turned on:
{
    "name": "Licht links",
    "type": "dimmable_light",
    "actions": ["light_off", "light_on", "stop", "wink"],
    "properties": {
        "actual_brightness": {
            "type": "numeric",
            "minimum": 0,
            "maximum": 65535,
            "value": 65535,
            "readonly": true
        },
        "dim_duration": {
            "type": "numeric",
            "minimum": 20,
            "maximum": 3600000,
            "value": 6000,
            "readonly": false
        },
        "target_brightness": {
            "type": "numeric",
            "minimum": 0,
            "maximum": 65535,
            "value": 65535,
            "readonly": false
        }
    }
}

I've called /events and performed the following:
1, light on, brightness +/- 50%
2, light off
3, light on, brightness 100%
4, light off
event: snapshot
data: {"devices":{"21e6048b-adf1-41b0-833f-82452cdc5fad":{"name":"Licht links","type":"dimmable_light","actions":["light_off","light_on","stop","wink"],"properties":{"actual_brightness":{"type":"numeric","minimum":0,"maximum":65535,"value":0,"readonly":true},"dim_duration":{"type":"numeric","minimum":20,"maximum":3600000,"value":500,"readonly":false},"target_brightness":{"type":"numeric","minimum":0,"maximum":65535,"value":0,"readonly":false}}}

event: patch
data: {"devices":{"21e6048b-adf1-41b0-833f-82452cdc5fad":{"properties":{"actual_brightness":{"animation":{"current_value":0,"keyframes":[{"delay":0,"duration":0.267689021,"interpolation":"linear","value":35086}],"start":1702300612.2786393}},"target_brightness":{"value":35086}}}}}

event: patch
data: {"devices":{"21e6048b-adf1-41b0-833f-82452cdc5fad":{"properties":{"actual_brightness":{"animation":{"current_value":35086,"keyframes":[{"delay":0,"duration":0.267689021,"interpolation":"linear","value":0}],"start":1702300614.7667885},"value":35086},"target_brightness":{"value":0}}}}}

event: patch
data: {"devices":{"21e6048b-adf1-41b0-833f-82452cdc5fad":{"properties":{"actual_brightness":{"animation":{"current_value":0,"keyframes":[{"delay":0,"duration":6,"interpolation":"linear","value":65535}],"start":1702300616.4780426},"value":0},"dim_duration":{"value":6000},"target_brightness":{"value":65535}}}}}

event: patch
data: {"devices":{"21e6048b-adf1-41b0-833f-82452cdc5fad":{"properties":{"actual_brightness":{"animation":{"current_value":65535,"keyframes":[{"delay":0,"duration":0.5,"interpolation":"linear","value":0}],"start":1702300623.9613662},"value":65535},"dim_duration":{"value":500},"target_brightness":{"value":0}}}}}

However this is going to be a bit tricky, I'll try to explain:
Whenever you turn on a light, it automatically goes to the last known brightness state. In my case, turning on the led brought it to +/- 50% brightness. When you want to change to 100%, you have to slide on the tile in the app and the brightness slowly increases in the selected direction. You have to klick again at the desired value, then the animation stops. When turning off and on again, it remembers that it was at 100% so there is no animation. Hope I made it understandable. Maybe you could neglect duration completely or set it to a fixed value? If you need anything hmu

awesome, thanks a lot for that data! 👍🏻
exactly, the duration was what i wanted to see and am more „concerned“ about.
i guess i could set it to a static value but my concerns are that if it‘s too low the brightness would jump from low to high value and vice-versa, and if it’s too high would take a long time to transition for a small change…
both is not entirely user friendly. however, seeing the set values it‘s somehow either 500 or 6000 - so maybe i can find some kind of way to set it sensibly for the user to not have an entirely jumping light. 😄
either way, as i can‘t test it myself, we‘ll probably need a few iterations to get the light integration right. i‘ll update you once i had some time and a new beta ready. 😉

@clostermannshof v8.0.0-beta.4 includes initial support for lights. it would be interesting to see if it shows up in HA, updates its state correctly, and what actions are working when performed through HA.

That was quick @muhlba91!
Unfortunately the lights are not visible in ha, neither as devices nor as entities.
However I can see them in the debug logs when reloading the ha integration:
2023-12-12 08:54:05.643 INFO (MainThread) [custom_components.hella_onyx.api_connector] Starting ONYX
2023-12-12 08:54:05.654 INFO (MainThread) [custom_components.hella_onyx.cover] adding 3 hella_onyx shutter entities
2023-12-12 08:54:05.658 INFO (MainThread) [custom_components.hella_onyx.sensor] adding 10 hella_onyx sensor entities
[...]
2023-12-12 08:54:06.004 DEBUG (MainThread) [custom_components.hella_onyx.api_connector] Received device update 21e6048b-adf1-41b0-833f-82452cdc5fad (<onyx_client.device.light.Light object at 0x7f8131a350>)

Any additional steps I should try?

this is interesting - i figured out why the lights are not taken. it was a while ago when i added a new platform.
i also tried it on my instance with only shutters, and that worked which hopefully means your shutters and weather station should have been working fine...
could you please try v8.0.0-beta.5 where i added the light platform for HA to recognize, and restart your HA afterward?

I tried and the lights showed up succesfully in ha! However no control is possible, the leds show up as sensors without control elements

debug says TypeError: unsupported operand type(s) for &: 'list' and 'LightEntityFeature'

thank you for the debug log! 👍
v8.0.0-beta.6 should fix this one now.

It appears with control elements now but doesn't react.
For the debug, I tried the following: Turn on, turn off, dimm to 100%, dimm to +/-30%, dimm to 0%
2023-12-12 11:50:15.218 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [548248381632] 'brightness'
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 238, in handle_call_service
    response = await hass.services.async_call(
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/core.py", line 2067, in async_call
    response_data = await coro
                    ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/core.py", line 2104, in _execute_service
    return await target(service_call)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 272, in handle_service
    return await service.entity_service_call(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 878, in entity_service_call
    single_response = await _handle_entity_call(
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 948, in _handle_entity_call
    result = await task
             ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/light/__init__.py", line 580, in async_handle_light_on_service
    await light.async_turn_on(**filter_turn_on_params(light, params))
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1279, in async_turn_on
    await self.hass.async_add_executor_job(ft.partial(self.turn_on, **kwargs))
  File "/usr/local/lib/python3.11/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/hella_onyx/sensors/light.py", line 89, in turn_on
    kwargs[ATTR_BRIGHTNESS] / 255 * self._device.actual_brightness.maximum
    ~~~~~~^^^^^^^^^^^^^^^^^
KeyError: 'brightness'
2023-12-12 11:50:17.974 DEBUG (SyncWorker_14) [custom_components.hella_onyx.sensors.light] turning light 21e6048b-adf1-41b0-833f-82452cdc5fad off
2023-12-12 11:50:17.978 INFO (MainThread) [custom_components.hella_onyx.api_connector] executing light_off for device 21e6048b-adf1-41b0-833f-82452cdc5fad
2023-12-12 11:50:21.384 DEBUG (SyncWorker_19) [custom_components.hella_onyx.sensors.light] setting brightness for light 21e6048b-adf1-41b0-833f-82452cdc5fad: 64764 (5935 ms)
2023-12-12 11:50:21.390 INFO (MainThread) [custom_components.hella_onyx.api_connector] executing {'target_brightness': 64764, 'dim_duration': 5935} for device 21e6048b-adf1-41b0-833f-82452cdc5fad
2023-12-12 11:50:21.494 DEBUG (MainThread) [custom_components.hella_onyx.api_connector] Received device update 21e6048b-adf1-41b0-833f-82452cdc5fad (Device(id=21e6048b-adf1-41b0-833f-82452cdc5fad, name=None, type=None))
2023-12-12 11:50:21.494 DEBUG (MainThread) [custom_components.hella_onyx] Manually updated ONYX data
2023-12-12 11:50:21.495 DEBUG (MainThread) [custom_components.hella_onyx.sensors.shutter] received position for device 4cc8635e-808c-44a1-aca5-7c670497665e: NumericValue(value=100, minimum=0, maximum=100, animation=None)
2023-12-12 11:50:21.496 DEBUG (MainThread) [custom_components.hella_onyx.sensors.shutter] received tilt position for device 4cc8635e-808c-44a1-aca5-7c670497665e: NumericValue(value=0, minimum=0, maximum=360, animation=None)
2023-12-12 11:50:21.496 DEBUG (MainThread) [custom_components.hella_onyx.sensors.shutter] received position for device 835857a1-304b-44b4-b4ea-586f0875462b: NumericValue(value=100, minimum=0, maximum=100, animation=None)
2023-12-12 11:50:21.497 DEBUG (MainThread) [custom_components.hella_onyx.sensors.shutter] received tilt position for device 835857a1-304b-44b4-b4ea-586f0875462b: NumericValue(value=0, minimum=0, maximum=360, animation=None)
2023-12-12 11:50:21.503 DEBUG (MainThread) [custom_components.hella_onyx.sensors.shutter] received position for device 32d88906-1d53-4eb8-be89-225c570c8625: NumericValue(value=100, minimum=0, maximum=100, animation=None)
2023-12-12 11:50:21.504 DEBUG (MainThread) [custom_components.hella_onyx.sensors.shutter] received tilt position for device 32d88906-1d53-4eb8-be89-225c570c8625: NumericValue(value=0, minimum=0, maximum=360, animation=None)
2023-12-12 11:50:24.038 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [548248381632] unsupported operand type(s) for -: 'int' and 'NoneType'
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 238, in handle_call_service
    response = await hass.services.async_call(
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/core.py", line 2067, in async_call
    response_data = await coro
                    ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/core.py", line 2104, in _execute_service
    return await target(service_call)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 272, in handle_service
    return await service.entity_service_call(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 878, in entity_service_call
    single_response = await _handle_entity_call(
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 948, in _handle_entity_call
    result = await task
             ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/light/__init__.py", line 580, in async_handle_light_on_service
    await light.async_turn_on(**filter_turn_on_params(light, params))
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1279, in async_turn_on
    await self.hass.async_add_executor_job(ft.partial(self.turn_on, **kwargs))
  File "/usr/local/lib/python3.11/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/hella_onyx/sensors/light.py", line 91, in turn_on
    dim_duration = self._get_dim_duration(hella_brightness)
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/hella_onyx/sensors/light.py", line 125, in _get_dim_duration
    (target - brightness.value)
     ~~~~~~~^~~~~~~~~~~~~~~~~~
TypeError: unsupported operand type(s) for -: 'int' and 'NoneType'
2023-12-12 11:50:27.701 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [548248381632] 'brightness'
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 238, in handle_call_service
    response = await hass.services.async_call(
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/core.py", line 2067, in async_call
    response_data = await coro
                    ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/core.py", line 2104, in _execute_service
    return await target(service_call)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 272, in handle_service
    return await service.entity_service_call(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 878, in entity_service_call
    single_response = await _handle_entity_call(
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 948, in _handle_entity_call
    result = await task
             ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/light/__init__.py", line 580, in async_handle_light_on_service
    await light.async_turn_on(**filter_turn_on_params(light, params))
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1279, in async_turn_on
    await self.hass.async_add_executor_job(ft.partial(self.turn_on, **kwargs))
  File "/usr/local/lib/python3.11/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/hella_onyx/sensors/light.py", line 89, in turn_on
    kwargs[ATTR_BRIGHTNESS] / 255 * self._device.actual_brightness.maximum
    ~~~~~~^^^^^^^^^^^^^^^^^
KeyError: 'brightness'

thank you for the debug logging and sorry for those errors...
would you be able to test v8.0.0-beta.7 by also restarting HA and enabling debug logging?
could you also try turning it on via the Onyx app and then dim it/turn it off via HA?

i didn't expect those lights to require so many tries, but here you go: v8.0.0-beta.8 should hopefully fix the state update.
once a command is issued, ONYX returns the animation (= the time it takes to finish the operation), and now i'll force a state update a little bit after that time passes. hence, i do hope that a state change will show up once that time passed.

Alright. They work very sporadically and no real error pattern is recognisable. I'll try to state a view

toggeling the switch on results in the light going on, a few ms later the switch in ha displays off (regularly)
another toggeling of the switch (displaying off) turns the light off
no reaction at all when toggeling the switch (sometimes)
when using the dimming function, the light dimms accordingly but displays being off (regularly)
dimming breaks the control (sometimes)
after dimming the on/off control is broken (regularly)
when using the onyx app the correct value is not brought into ha and the light is displayed as off (sometimes)

I even had a funny glitch where the brightness of the light was displayed as 6550% in ha. But that was an exception
Logs are very difficult to filter at this point but I'll try to break them down a little bit 😕
2023-12-12 16:36:00.582 ERROR (MainThread) [onyx_client.client] Unexpected exception: RuntimeError('Cannot be called from within the event loop'). Retrying with backoff 24s.
2023-12-12 16:36:25.084 ERROR (MainThread) [onyx_client.client] Unexpected exception: RecursionError('maximum recursion depth exceeded'). Retrying with backoff 26s.
2023-12-12 16:38:02.295 ERROR (MainThread) [onyx_client.client] Unexpected exception: RuntimeError('Cannot be called from within the event loop'). Retrying with backoff 47s.
2023-12-12 16:39:08.464 ERROR (MainThread) [onyx_client.client] Unexpected exception: RuntimeError('Cannot be called from within the event loop'). Retrying with backoff 44s.
2023-12-12 16:40:16.687 DEBUG (SyncWorker_8) [custom_components.hella_onyx.sensors.light] turning light 21e6048b-adf1-41b0-833f-82452cdc5fad on
2023-12-12 16:40:16.691 INFO (MainThread) [custom_components.hella_onyx.api_connector] executing light_on for device 21e6048b-adf1-41b0-833f-82452cdc5fad
2023-12-12 16:40:16.775 DEBUG (MainThread) [custom_components.hella_onyx.api_connector] Received device update 21e6048b-adf1-41b0-833f-82452cdc5fad (Light(Device(id=21e6048b-adf1-41b0-833f-82452cdc5fad, name=None, type=None), actual_brightness=NumericValue(value=14645, minimum=0, maximum=100, animation=None), target_brightness=None, dim_duration=None))
2023-12-12 16:40:16.776 DEBUG (MainThread) [custom_components.hella_onyx] Manually updated ONYX data
[...]
2023-12-12 16:40:16.780 DEBUG (MainThread) [custom_components.hella_onyx.sensors.light] received brightness for light 21e6048b-adf1-41b0-833f-82452cdc5fad: NumericValue(value=14645, minimum=0, maximum=100, animation=None)
2023-12-12 16:40:16.784 DEBUG (MainThread) [custom_components.hella_onyx.sensors.light] received brightness for light 2609269a-cc71-4a72-8d58-db72ec733dbc: NumericValue(value=6550, minimum=0, maximum=65535, animation=None)
2023-12-12 16:40:16.785 DEBUG (MainThread) [custom_components.hella_onyx.sensors.light] received brightness for light b1dcfe00-9fb0-470a-8c78-f9da47af3995: NumericValue(value=32306, minimum=0, maximum=65535, animation=None)
2023-12-12 16:40:16.785 DEBUG (MainThread) [custom_components.hella_onyx.sensors.shutter] received position for device 32d88906-1d53-4eb8-be89-225c570c8625: NumericValue(value=100, minimum=0, maximum=100, animation=None)
2023-12-12 16:40:16.786 DEBUG (MainThread) [custom_components.hella_onyx.sensors.shutter] received tilt position for device 32d88906-1d53-4eb8-be89-225c570c8625: NumericValue(value=0, minimum=0, maximum=360, animation=None)
2023-12-12 16:40:19.102 DEBUG (SyncWorker_6) [custom_components.hella_onyx.sensors.light] turning light 21e6048b-adf1-41b0-833f-82452cdc5fad off
2023-12-12 16:40:19.106 INFO (MainThread) [custom_components.hella_onyx.api_connector] executing light_off for device 21e6048b-adf1-41b0-833f-82452cdc5fad
2023-12-12 16:40:19.189 DEBUG (MainThread) [custom_components.hella_onyx.api_connector] Received device update 21e6048b-adf1-41b0-833f-82452cdc5fad (Light(Device(id=21e6048b-adf1-41b0-833f-82452cdc5fad, name=None, type=None), actual_brightness=NumericValue(value=None, minimum=0, maximum=100, animation=AnimationValue(start=1702395619.1728034, current_value=14645, #keyframes=1)), target_brightness=NumericValue(value=0, minimum=0, maximum=100, animation=None), dim_duration=None))
2023-12-12 16:40:19.190 DEBUG (MainThread) [custom_components.hella_onyx] Manually updated ONYX data
[...]
2023-12-12 16:40:22.398 DEBUG (MainThread) [custom_components.hella_onyx.sensors.light] received brightness for light 21e6048b-adf1-41b0-833f-82452cdc5fad: NumericValue(value=14645, minimum=0, maximum=100, animation=AnimationValue(start=1702395622.373864, current_value=14645, #keyframes=1))
2023-12-12 16:40:22.399 DEBUG (MainThread) [custom_components.hella_onyx.sensors.light] updating device 21e6048b-adf1-41b0-833f-82452cdc5fad with current_time<PHONE_NUMBER>.3995671 and end_time<PHONE_NUMBER>.485598: True
2023-12-12 16:40:22.400 ERROR (MainThread) [onyx_client.client] Unexpected exception: RuntimeError('Cannot be called from within the event loop'). Retrying with backoff 9s.
2023-12-12 16:40:22.835 DEBUG (SyncWorker_16) [custom_components.hella_onyx.sensors.light] turning light 21e6048b-adf1-41b0-833f-82452cdc5fad on
2023-12-12 16:40:22.873 INFO (MainThread) [custom_components.hella_onyx.api_connector] executing light_on for device 21e6048b-adf1-41b0-833f-82452cdc5fad
2023-12-12 16:40:23.425 DEBUG (SyncWorker_11) [custom_components.hella_onyx.sensors.light] turning light 21e6048b-adf1-41b0-833f-82452cdc5fad off
2023-12-12 16:40:23.429 INFO (MainThread) [custom_components.hella_onyx.api_connector] executing light_off for device 21e6048b-adf1-41b0-833f-82452cdc5fad
2023-12-12 16:40:23.820 DEBUG (SyncWorker_19) [custom_components.hella_onyx.sensors.light] turning light 21e6048b-adf1-41b0-833f-82452cdc5fad on
2023-12-12 16:40:23.823 INFO (MainThread) [custom_components.hella_onyx.api_connector] executing light_on for device 21e6048b-adf1-41b0-833f-82452cdc5fad
2023-12-12 16:40:24.318 DEBUG (SyncWorker_12) [custom_components.hella_onyx.sensors.light] turning light 21e6048b-adf1-41b0-833f-82452cdc5fad off
2023-12-12 16:40:24.322 INFO (MainThread) [custom_components.hella_onyx.api_connector] executing light_off for device 21e6048b-adf1-41b0-833f-82452cdc5fad
2023-12-12 16:40:24.777 DEBUG (SyncWorker_0) [custom_components.hella_onyx.sensors.light] turning light 21e6048b-adf1-41b0-833f-82452cdc5fad on
2023-12-12 16:40:24.781 INFO (MainThread) [custom_components.hella_onyx.api_connector] executing light_on for device 21e6048b-adf1-41b0-833f-82452cdc5fad
2023-12-12 16:40:26.017 DEBUG (SyncWorker_13) [custom_components.hella_onyx.sensors.light] setting brightness for light 21e6048b-adf1-41b0-833f-82452cdc5fad: 55 (801950 ms)
2023-12-12 16:40:26.024 INFO (MainThread) [custom_components.hella_onyx.api_connector] executing {'target_brightness': 55, 'dim_duration': 801950} for device 21e6048b-adf1-41b0-833f-82452cdc5fad
2023-12-12 16:40:28.839 DEBUG (SyncWorker_20) [custom_components.hella_onyx.sensors.light] setting brightness for light 21e6048b-adf1-41b0-833f-82452cdc5fad: 79 (800630 ms)
2023-12-12 16:40:28.841 INFO (MainThread) [custom_components.hella_onyx.api_connector] executing {'target_brightness': 79, 'dim_duration': 800630} for device 21e6048b-adf1-41b0-833f-82452cdc5fad
2023-12-12 16:40:30.552 DEBUG (MainThread) [custom_components.hella_onyx.api_connector] Received device update df5cd297-095a-4cae-8573-4db506de39a5 (Weather(Device(id=df5cd297-095a-4cae-8573-4db506de39a5, name=None, type=None), wind_peak=None, sun_brightness_peak=None, sun_brightness_sink=NumericValue(value=46, minimum=0, maximum=100, animation=None), air_pressure=NumericValue(value=98849, minimum=0, maximum=100, animation=None), humidity=None, temperature=None))
2023-12-12 16:40:30.553 DEBUG (MainThread) [custom_components.hella_onyx] Manually updated ONYX data
[...]
2023-12-12 16:40:30.737 DEBUG (MainThread) [custom_components.hella_onyx.api_connector] Received device update df5cd297-095a-4cae-8573-4db506de39a5 (Weather(Device(id=df5cd297-095a-4cae-8573-4db506de39a5, name=None, type=None), wind_peak=None, sun_brightness_peak=None, sun_brightness_sink=None, air_pressure=NumericValue(value=98848, minimum=0, maximum=100, animation=None), humidity=None, temperature=None))
[...]
2023-12-12 16:40:30.804 DEBUG (SyncWorker_1) [custom_components.hella_onyx.sensors.light] setting brightness for light 21e6048b-adf1-41b0-833f-82452cdc5fad: 31 (803269 ms)
2023-12-12 16:40:30.810 INFO (MainThread) [custom_components.hella_onyx.api_connector] executing {'target_brightness': 31, 'dim_duration': 803269} for device 21e6048b-adf1-41b0-833f-82452cdc5fad
2023-12-12 16:40:31.721 DEBUG (MainThread) [custom_components.hella_onyx.api_connector] Received device update 21e6048b-adf1-41b0-833f-82452cdc5fad (Light(Device(id=21e6048b-adf1-41b0-833f-82452cdc5fad, name=Licht links, type=DeviceType.DIMMABLE_LIGHT), actual_brightness=NumericValue(value=14645, minimum=0, maximum=65535, animation=AnimationValue(start=1702395630.8668613, current_value=14645, #keyframes=1)), target_brightness=NumericValue(value=31, minimum=0, maximum=65535, animation=None), dim_duration=NumericValue(value=803269, minimum=20, maximum=3600000, animation=None)))
[...]
2023-12-12 16:40:31.727 DEBUG (MainThread) [custom_components.hella_onyx.sensors.light] received brightness for light 21e6048b-adf1-41b0-833f-82452cdc5fad: NumericValue(value=14645, minimum=0, maximum=65535, animation=AnimationValue(start=1702395630.8668613, current_value=14645, #keyframes=1))
2023-12-12 16:40:31.727 DEBUG (MainThread) [custom_components.hella_onyx.sensors.light] updating device 21e6048b-adf1-41b0-833f-82452cdc5fad with current_time<PHONE_NUMBER>.7275898 and end_time<PHONE_NUMBER>.99211: True
2023-12-12 16:40:31.729 ERROR (MainThread) [onyx_client.client] Unexpected exception: RuntimeError('Cannot be called from within the event loop'). Retrying with backoff 42s.
2023-12-12 16:40:32.506 DEBUG (SyncWorker_11) [custom_components.hella_onyx.sensors.light] turning light 21e6048b-adf1-41b0-833f-82452cdc5fad on
2023-12-12 16:40:32.509 INFO (MainThread) [custom_components.hella_onyx.api_connector] executing light_on for device 21e6048b-adf1-41b0-833f-82452cdc5fad
2023-12-12 16:40:33.933 DEBUG (SyncWorker_12) [custom_components.hella_onyx.sensors.light] turning light 21e6048b-adf1-41b0-833f-82452cdc5fad off
2023-12-12 16:40:33.936 INFO (MainThread) [custom_components.hella_onyx.api_connector] executing light_off for device 21e6048b-adf1-41b0-833f-82452cdc5fad
2023-12-12 16:40:34.523 DEBUG (SyncWorker_0) [custom_components.hella_onyx.sensors.light] turning light 21e6048b-adf1-41b0-833f-82452cdc5fad on
2023-12-12 16:40:34.527 INFO (MainThread) [custom_components.hella_onyx.api_connector] executing light_on for device 21e6048b-adf1-41b0-833f-82452cdc5fad
2023-12-12 16:40:36.884 DEBUG (SyncWorker_4) [custom_components.hella_onyx.sensors.light] setting brightness for light 21e6048b-adf1-41b0-833f-82452cdc5fad: 65535 (4770 ms)
2023-12-12 16:40:36.894 INFO (MainThread) [custom_components.hella_onyx.api_connector] executing {'target_brightness': 65535, 'dim_duration': 4770} for device 21e6048b-adf1-41b0-833f-82452cdc5fad
2023-12-12 16:40:43.147 DEBUG (SyncWorker_8) [custom_components.hella_onyx.sensors.light] setting brightness for light 21e6048b-adf1-41b0-833f-82452cdc5fad: 31354 (1902 ms)
2023-12-12 16:40:43.153 INFO (MainThread) [custom_components.hella_onyx.api_connector] executing {'target_brightness': 31354, 'dim_duration': 1902} for device 21e6048b-adf1-41b0-833f-82452cdc5fad
2023-12-12 16:40:45.289 DEBUG (SyncWorker_6) [custom_components.hella_onyx.sensors.light] turning light 21e6048b-adf1-41b0-833f-82452cdc5fad on
2023-12-12 16:40:45.293 INFO (MainThread) [custom_components.hella_onyx.api_connector] executing light_on for device 21e6048b-adf1-41b0-833f-82452cdc5fad
2023-12-12 16:40:47.925 DEBUG (SyncWorker_20) [custom_components.hella_onyx.sensors.light] turning light 21e6048b-adf1-41b0-833f-82452cdc5fad on
2023-12-12 16:40:47.929 INFO (MainThread) [custom_components.hella_onyx.api_connector] executing light_on for device 21e6048b-adf1-41b0-833f-82452cdc5fad
2023-12-12 16:40:49.052 DEBUG (SyncWorker_1) [custom_components.hella_onyx.sensors.light] turning light 21e6048b-adf1-41b0-833f-82452cdc5fad off
2023-12-12 16:40:49.056 INFO (MainThread) [custom_components.hella_onyx.api_connector] executing light_off for device 21e6048b-adf1-41b0-833f-82452cdc5fad
2023-12-12 16:40:50.656 DEBUG (SyncWorker_16) [custom_components.hella_onyx.sensors.light] turning light 21e6048b-adf1-41b0-833f-82452cdc5fad on
2023-12-12 16:40:50.659 INFO (MainThread) [custom_components.hella_onyx.api_connector] executing light_on for device 21e6048b-adf1-41b0-833f-82452cdc5fad
2023-12-12 16:40:51.623 DEBUG (SyncWorker_11) [custom_components.hella_onyx.sensors.light] turning light 21e6048b-adf1-41b0-833f-82452cdc5fad on
2023-12-12 16:40:51.631 INFO (MainThread) [custom_components.hella_onyx.api_connector] executing light_on for device 21e6048b-adf1-41b0-833f-82452cdc5fad
2023-12-12 16:40:52.718 DEBUG (SyncWorker_19) [custom_components.hella_onyx.sensors.light] turning light 21e6048b-adf1-41b0-833f-82452cdc5fad on
2023-12-12 16:40:52.722 INFO (MainThread) [custom_components.hella_onyx.api_connector] executing light_on for device 21e6048b-adf1-41b0-833f-82452cdc5fad
2023-12-12 16:40:55.013 DEBUG (SyncWorker_9) [custom_components.hella_onyx.sensors.light] turning light 21e6048b-adf1-41b0-833f-82452cdc5fad on
2023-12-12 16:40:55.019 INFO (MainThread) [custom_components.hella_onyx.api_connector] executing light_on for device 21e6048b-adf1-41b0-833f-82452cdc5fad
2023-12-12 16:40:57.859 DEBUG (SyncWorker_5) [custom_components.hella_onyx.sensors.light] setting brightness for light 21e6048b-adf1-41b0-833f-82452cdc5fad: 50372 (3498 ms)
2023-12-12 16:40:57.865 INFO (MainThread) [custom_components.hella_onyx.api_connector] executing {'target_brightness': 50372, 'dim_duration': 3498} for device 21e6048b-adf1-41b0-833f-82452cdc5fad
2023-12-12 16:40:59.291 DEBUG (SyncWorker_3) [custom_components.hella_onyx.sensors.light] turning light 21e6048b-adf1-41b0-833f-82452cdc5fad on
2023-12-12 16:40:59.296 INFO (MainThread) [custom_components.hella_onyx.api_connector] executing light_on for device 21e6048b-adf1-41b0-833f-82452cdc5fad
2023-12-12 16:41:00.536 DEBUG (MainThread) [custom_components.hella_onyx] Manually updated ONYX data
[...]
2023-12-12 16:41:02.947 DEBUG (SyncWorker_2) [custom_components.hella_onyx.sensors.light] setting brightness for light 21e6048b-adf1-41b0-833f-82452cdc5fad: 15163 (543 ms)
2023-12-12 16:41:02.954 INFO (MainThread) [custom_components.hella_onyx.api_connector] executing {'target_brightness': 15163, 'dim_duration': 543} for device 21e6048b-adf1-41b0-833f-82452cdc5fad
2023-12-12 16:41:04.957 DEBUG (SyncWorker_7) [custom_components.hella_onyx.sensors.light] turning light 21e6048b-adf1-41b0-833f-82452cdc5fad on
2023-12-12 16:41:04.966 INFO (MainThread) [custom_components.hella_onyx.api_connector] executing light_on for device 21e6048b-adf1-41b0-833f-82452cdc5fad
2023-12-12 16:41:07.725 DEBUG (SyncWorker_12) [custom_components.hella_onyx.sensors.light] turning light 21e6048b-adf1-41b0-833f-82452cdc5fad on
2023-12-12 16:41:07.729 INFO (MainThread) [custom_components.hella_onyx.api_connector] executing light_on for device 21e6048b-adf1-41b0-833f-82452cdc5fad
2023-12-12 16:41:10.343 DEBUG (SyncWorker_10) [custom_components.hella_onyx.sensors.light] turning light 21e6048b-adf1-41b0-833f-82452cdc5fad on
2023-12-12 16:41:10.348 INFO (MainThread) [custom_components.hella_onyx.api_connector] executing light_on for device 21e6048b-adf1-41b0-833f-82452cdc5fad
2023-12-12 16:41:12.966 DEBUG (SyncWorker_17) [custom_components.hella_onyx.sensors.light] setting brightness for light 21e6048b-adf1-41b0-833f-82452cdc5fad: 771 (664 ms)
2023-12-12 16:41:12.970 INFO (MainThread) [custom_components.hella_onyx.api_connector] executing {'target_brightness': 771, 'dim_duration': 664} for device 21e6048b-adf1-41b0-833f-82452cdc5fad
2023-12-12 16:41:14.042 DEBUG (MainThread) [custom_components.hella_onyx.api_connector] Received device update 21e6048b-adf1-41b0-833f-82452cdc5fad (Light(Device(id=21e6048b-adf1-41b0-833f-82452cdc5fad, name=Licht links, type=DeviceType.DIMMABLE_LIGHT), actual_brightness=NumericValue(value=15163, minimum=0, maximum=65535, animation=AnimationValue(start=1702395673.0302012, current_value=15163, #keyframes=1)), target_brightness=NumericValue(value=771, minimum=0, maximum=65535, animation=None), dim_duration=NumericValue(value=664, minimum=20, maximum=3600000, animation=None)))
2023-12-12 16:41:14.043 DEBUG (MainThread) [custom_components.hella_onyx] Manually updated ONYX data
2023-12-12 16:41:14.044 DEBUG (MainThread) [custom_components.hella_onyx.sensors.shutter] received position for device 4cc8635e-808c-44a1-aca5-7c670497665e: NumericValue(value=100, minimum=0, maximum=100, animation=None)
2023-12-12 16:41:14.045 DEBUG (MainThread) [custom_components.hella_onyx.sensors.shutter] received tilt position for device 4cc8635e-808c-44a1-aca5-7c670497665e: NumericValue(value=0, minimum=0, maximum=360, animation=None)
2023-12-12 16:41:14.045 DEBUG (MainThread) [custom_components.hella_onyx.sensors.shutter] received position for device 835857a1-304b-44b4-b4ea-586f0875462b: NumericValue(value=100, minimum=0, maximum=100, animation=None)
2023-12-12 16:41:14.046 DEBUG (MainThread) [custom_components.hella_onyx.sensors.shutter] received tilt position for device 835857a1-304b-44b4-b4ea-586f0875462b: NumericValue(value=0, minimum=0, maximum=360, animation=None)
2023-12-12 16:41:14.049 DEBUG (MainThread) [custom_components.hella_onyx.sensors.light] received brightness for light 21e6048b-adf1-41b0-833f-82452cdc5fad: NumericValue(value=15163, minimum=0, maximum=65535, animation=AnimationValue(start=1702395673.0302012, current_value=15163, #keyframes=1))
2023-12-12 16:41:14.050 DEBUG (MainThread) [custom_components.hella_onyx.sensors.light] updating device 21e6048b-adf1-41b0-833f-82452cdc5fad with current_time<PHONE_NUMBER>.0506237 and end_time<PHONE_NUMBER>.1760209: False
2023-12-12 16:41:14.051 DEBUG (MainThread) [custom_components.hella_onyx.sensors.light] end update device 21e6048b-adf1-41b0-833f-82452cdc5fad due to too old data
2023-12-12 16:41:14.051 DEBUG (MainThread) [custom_components.hella_onyx.sensors.light] calling stop to force update device 21e6048b-adf1-41b0-833f-82452cdc5fad
2023-12-12 16:41:14.052 DEBUG (MainThread) [custom_components.hella_onyx.sensors.light] received brightness for light 21e6048b-adf1-41b0-833f-82452cdc5fad: NumericValue(value=15163, minimum=0, maximum=65535, animation=AnimationValue(start=1702395673.0302012, current_value=15163, #keyframes=1))
2023-12-12 16:41:14.052 DEBUG (MainThread) [custom_components.hella_onyx.sensors.light] updating device 21e6048b-adf1-41b0-833f-82452cdc5fad with current_time<PHONE_NUMBER>.0528474 and end_time<PHONE_NUMBER>.1760209: False
2023-12-12 16:41:14.053 DEBUG (MainThread) [custom_components.hella_onyx.sensors.light] end update device 21e6048b-adf1-41b0-833f-82452cdc5fad due to too old data
2023-12-12 16:41:14.053 DEBUG (MainThread) [custom_components.hella_onyx.sensors.light] calling stop to force update device 21e6048b-adf1-41b0-833f-82452cdc5fad
2023-12-12 16:41:14.054 DEBUG (MainThread) [custom_components.hella_onyx.sensors.light] received brightness for light 21e6048b-adf1-41b0-833f-82452cdc5fad: NumericValue(value=15163, minimum=0, maximum=65535, animation=AnimationValue(start=1702395673.0302012, current_value=15163, #keyframes=1))
2023-12-12 16:41:14.054 DEBUG (MainThread) [custom_components.hella_onyx.sensors.light] updating device 21e6048b-adf1-41b0-833f-82452cdc5fad with current_time<PHONE_NUMBER>.0544014 and end_time<PHONE_NUMBER>.1760209: False
2023-12-12 16:41:14.054 DEBUG (MainThread) [custom_components.hella_onyx.sensors.light] end update device 21e6048b-adf1-41b0-833f-82452cdc5fad due to too old data
2023-12-12 16:41:14.054 DEBUG (MainThread) [custom_components.hella_onyx.sensors.light] calling stop to force update device 21e6048b-adf1-41b0-833f-82452cdc5fad
2023-12-12 16:41:14.055 DEBUG (MainThread) [custom_components.hella_onyx.sensors.light] received brightness for light 21e6048b-adf1-41b0-833f-82452cdc5fad: NumericValue(value=15163, minimum=0, maximum=65535, animation=AnimationValue(start=1702395673.0302012, current_value=15163, #keyframes=1))
2023-12-12 16:41:14.055 DEBUG (MainThread) [custom_components.hella_onyx.sensors.light] updating device 21e6048b-adf1-41b0-833f-82452cdc5fad with current_time<PHONE_NUMBER>.055686 and end_time<PHONE_NUMBER>.1760209: False
2023-12-12 16:41:14.055 DEBUG (MainThread) [custom_components.hella_onyx.sensors.light] end update device 21e6048b-adf1-41b0-833f-82452cdc5fad due to too old data
[...]
2023-12-12 16:41:14.343 DEBUG (MainThread) [custom_components.hella_onyx.sensors.light] received brightness for light 21e6048b-adf1-41b0-833f-82452cdc5fad: NumericValue(value=15163, minimum=0, maximum=65535, animation=AnimationValue(start=1702395673.0302012, current_value=15163, #keyframes=1))
2023-12-12 16:41:14.343 DEBUG (MainThread) [custom_components.hella_onyx.sensors.light] updating device 21e6048b-adf1-41b0-833f-82452cdc5fad with current_time<PHONE_NUMBER>.34326 and end_time<PHONE_NUMBER>.1760209: False
2023-12-12 16:41:14.343 DEBUG (MainThread) [custom_components.hella_onyx.sensors.light] end update device 21e6048b-adf1-41b0-833f-82452cdc5fad due to too old data
2023-12-12 16:41:14.343 DEBUG (MainThread) [custom_components.hella_onyx.sensors.light] calling stop to force update device 21e6048b-adf1-41b0-833f-82452cdc5fad
2023-12-12 16:41:14.369 ERROR (MainThread) [onyx_client.client] Unexpected exception: RecursionError('maximum recursion depth exceeded while calling a Python object'). Retrying with backoff 58s.
2023-12-12 16:41:14.394 INFO (MainThread) [custom_components.hella_onyx.api_connector] executing stop for device 21e6048b-adf1-41b0-833f-82452cdc5fad
2023-12-12 16:41:14.396 INFO (MainThread) [custom_components.hella_onyx.api_connector] executing stop for device 21e6048b-adf1-41b0-833f-82452cdc5fad
2023-12-12 16:41:14.398 INFO (MainThread) [custom_components.hella_onyx.api_connector] executing stop for device 21e6048b-adf1-41b0-833f-82452cdc5fad
2023-12-12 16:41:14.400 INFO (MainThread) [custom_components.hella_onyx.api_connector] executing stop for device 21e6048b-adf1-41b0-833f-82452cdc5fad
2023-12-12 16:41:14.402 INFO (MainThread) [custom_components.hella_onyx.api_connector] executing stop for device 21e6048b-adf1-41b0-833f-82452cdc5fad
2023-12-12 16:41:14.403 INFO (MainThread) [custom_components.hella_onyx.api_connector] executing stop for device 21e6048b-adf1-41b0-833f-82452cdc5fad
2023-12-12 16:41:14.405 INFO (MainThread) [custom_components.hella_onyx.api_connector] executing stop for device 21e6048b-adf1-41b0-833f-82452cdc5fad
[...]
2023-12-12 16:41:14.692 INFO (MainThread) [custom_components.hella_onyx.api_connector] executing stop for device 21e6048b-adf1-41b0-833f-82452cdc5fad
2023-12-12 16:41:14.694 INFO (MainThread) [custom_components.hella_onyx.api_connector] executing stop for device 21e6048b-adf1-41b0-833f-82452cdc5fad
2023-12-12 16:41:17.056 DEBUG (SyncWorker_13) [custom_components.hella_onyx.sensors.light] turning light 21e6048b-adf1-41b0-833f-82452cdc5fad on
2023-12-12 16:41:17.080 INFO (MainThread) [custom_components.hella_onyx.api_connector] executing light_on for device 21e6048b-adf1-41b0-833f-82452cdc5fad

this is an interesting one...
may i ask you for a favor? 😄 could you open a request to the /events endpoint, perform the actions, and post the HA logs and the endpoint responses?
performing some simple actions that lead to an error should do. e.g., turn on, dim to a low value, dim to a higher value, turn off, turn on, dim to lower value (hoping we see this behaviour then).
additionally, it would be cool if you could do it twice:

perform an action, wait e.g. 15-30seconds before you perform the next one
perform all actions somehow quick after each other - maybe dim it a couple of times within a few secs

quick update: i think i found a cause for some of that weird behaviour. i‘ll dig deeper tomorrow and probably push another beta later tomorrow.

@clostermannshof if you would like to have another round of testing: v8.0.0-beta.10 😅
1/ could you please perform actions with some wait time in between?
i'd like to see if actions are executed, and the state gets updated ~1 second after the transition is finished.
2/ if this would work already, please try dimming multiple times but relatively quickly after the previous one - it probably happens that the slider will jump in between to update its value, but, again, ~1 second after the last action was executed i'd hope that the entity adjusts correctly.
the reason here is that - from the data you sent and my experience with the shutters - Hella doesn't provide a final update once the transition is done. for that, i need to create a background timer and call "STOP" on the light to get the final update. well, i can't just call stop if someone tried to set a new value in the meantime. imagine a transition takes 10 seconds, and you trigger a new one after 5 seconds. the first timer would run out 5 seconds afterward and stop the dimming; hence, i now try to determine if this was the end of all transitions and call stop then; alternatively, interpolate the value at that time for the light until the last timer determines that the transition is over and calls stop.
additionally, i added a 1-second delay to triggering this evaluation, which i'd like to reduce a bit in the future. it should just provide a safety delay for any potential time calculation differences.
i do believe that some of the found errors happened because of incorrectly handling the updates - first, i ran into an endless loop, and, secondly, i assumed the light would send an update if it's finished dimming (which your data doesn't confirm).
the dim duration of > 80000 you received in your logs still makes me struggle. i could not find a valid test case that leads to this one...

@muhlba91 we got some improvements here but not continuous.
turning on / off had improved drastically! light reacts nearly realtime so that is a big plus!
However there is one problem but I could see a regularity here.
Turning on results in the light immediatly turning on, switch in ha displays on
However after the delay on 1s the switch in ha displays off again.
When pressing the switch again, light does nothing, however switch displays on now and stays like that.
Now when pressing the switch (off) the light immediatly turns off.
After that the switch stays off -> correctly
I repeated this like 20 times, always the same behavior of the switch going to the off state after 1s and hence the light not reacting when pressing it the second time.
It gets interesting when I toggle the light on and off multiple times per second. The switch has no time going back to the wrong state bc i already pressed it <1s. In this scenario, the light goes on and off without any problems and i real time.
Now to the bigger problem: dimming.
I got it to work a little bit in the beginning but hadn't the debug on at that time.
Later dimming was completely broken, resulting in the light going off when dimming or doing nothing at all, hope debug helps. And the glitch with 6550%, 3520% etc happened a lot this time. With dimming there also was no difference when giving it time compared to multiple inputs per second.
Logs 2023-12-13.txt

awesome log capture, especially such a long one; highly appreciated! 👍
i'll see if i can push another update by tomorrow; otherwise, hopefully, on monday. i'll update you when i have news.

@muhlba91 no problem 😄
for me (but please don't blame me if I totally scratch the surface here... 😟) it looks like the dimming problem lies in the difference between hellas values 0 - 65535 and ha percentage 0 - 100
e.g. here received brightness for light 21e6048b-adf1-41b0-833f-82452cdc5fad: NumericValue(value=6550, minimum=0, maximum=100 brightness NumericValue is expected to be max 100 but is 6550
On/off is only done through light_off and light_on hence working

yes, you are right; exactly that is the problem. funnily that issue is also happening for raffstore tilt angles but since those angles are pretty close to 100 anyway it's not visible to the user - also, a small difference in an angle doesn't really have a lot of visible implications. 😅
this requires a change in the client library, though, which i need to test more thoroughly, and will take a bit to include all required changes correctly.
to be even more precise, the problem with the values arises because hella's streaming endpoint doesn't return the entire actual brightness but only the immediate updates. in the library a default of 100 is chosen if no maximum value was specified which is not correct for lights. 🙈
hence, i need to refactor the merge process when an update arrives via the endpoint to apply a more in-depth merging strategy.

Annoying but somehow very interesting, thanks for the explanation! I just saw that the automatic choice of 100 as max is just with "Licht links" which I used to test all the time. The other lights which I didn't touch at all had NumericValue of 65535
2023-12-13 17:02:58.390 DEBUG (HellaOnyx) [custom_components.hella_onyx.sensors.light] received brightness for light 21e6048b-adf1-41b0-833f-82452cdc5fad: NumericValue(value=6550, minimum=0, maximum=100, animation=None)
2023-12-13 17:02:58.393 DEBUG (HellaOnyx) [custom_components.hella_onyx.sensors.light] received brightness for light 2609269a-cc71-4a72-8d58-db72ec733dbc: NumericValue(value=65535, minimum=0, maximum=65535, animation=None)
2023-12-13 17:02:58.394 DEBUG (HellaOnyx) [custom_components.hella_onyx.sensors.light] received brightness for light b1dcfe00-9fb0-470a-8c78-f9da47af3995: NumericValue(value=65535, minimum=0, maximum=65535, animation=None)

Looking forward to your update! 👍

i just pushed v8.0.0-beta.11 for a new test run. 😉
i refactored much of the update handling, and the shutters seem stable. let's see how it behaves for your lights.
it would be awesome to try one of your shutters as a second person looking at it; it was a pretty heavy change in how all updates are processed now. 😃

Already tested 🤙
pergola works fine respectively even better bc the buttons in ha are updated faster and more reliably.
light_off and light_on also work now including the button displaying the correct state!
However.... dimming does absolutely nothing, logs attached.
I noticed the following when scanning the logs:
dim_duration=NumericValue(value=358000, minimum=0, maximum=100, animation=None)
actual_brightness=NumericValue(value=5980, minimum=0, maximum=100, [...])
error_log-3.txt

cool, that's great to hear that this works better now, and the light on/off works without issues! 👍
as for the dimming, i'm sorry as this was a pretty stupid mistake on my side to forget to remove default values everywhere - too many changes happening... could you try out v8.0.0-beta.12? i hope the maximum will be set correctly with this one which should fix some issues now.

@muhlba91 damn it runs so smoothly! 🙏
Didn't encounter any problems this time! Everything is displayed correctly and the status in ha also updates when making changes in the onyx app! If I had a wish it would be to reduce the dim_duration a little bit to get more of a responsiveness feeling but that is just a personal feeling.
Attached the logs if you want to countercheck 😄
error_log-4.txt

sorry for the late reply I was not able to test earlier.
1/ lights still are working perfectly fine
2/ the set dim duration is not applied, I tested both extremes and there was no change noticable

no worries - thanks a lot for your testing support! 👍
v8.0.0-beta.14 should fix the non-applying configuration now.

v8.0.0-beta.14 definitely fixed that! 🙏
I tested both very short and long dim_duration, everything was applied correctly. I found 200 and 2000 to be good default values where the light reacts responsive but still with a pleasant transition.
Think we are ready for final release? 🥳

i have applied your suggestion as the default values now.
the user can then adjust them according to his/her preferences, anyway.
that means: v8.0.0 has been released, and i highly appreciate your patience and support! 🥳
with that, i'm also closing this issue.


create.env

exemple

Thanks, but I don't want any .env files in the repo because users might check their secrets accidentally and leak them.


Strange behaviour when MAX_RUN_TIME is exceeded

Tasks seem to be locked but not executed when MAX_RUN_TIME is exceeded.

Tasks will be restarted if MAX_RUN_TIME is exceeded.


gpgme needs a new maintainer

I removed myself as maintainer in #128098. Would anyone be interested to maintain it?

I've opened this issue because gpgme is an important and security-critical library but such issues are of little use (especially if they're old) so I'll go ahead and close it.
Still an issue though:
nix-repl> gpgme.meta.maintainers
[ ]


Dice coef from model.evaluate() , and model.predict() is different.

I'm using keras for biomedical image segmentation.
When evaluating the model I used model.evaluate() it gives me  Dice coef: 0.913. However, when I used model.predict() and compute the dice coef for the predicted images, the dice coef in this case is 0.797.
any idea?
Thanks.

Hi @saeedalahmari3, do you use the same dice function you used in training to also evaluate the predictions?


bug in DataFeeder constructor

System information

centos 7.0
python 3.4
tensorflow 1.2.1

Describe the problem
When I call tensorflow.contrib.learn.DNNRegressor.fit(x_train_dict , y_train,steps=1000)  , x_train_dict is dict  and y_train is array , the program throws the following exception:
File "/home/star/yuce.ddxq.mobi/zhuge/management/commands/forecast_product_sale.py", line 148, in tflearn_dnn_train2
    regressor.fit(x_train_dict, y_train, steps=10000, batch_size=10)
  File "/usr/lib/python3.4/site-packages/tensorflow/python/util/deprecation.py", line 289, in new_func
    return func(*args, **kwargs)
  File "/usr/lib/python3.4/site-packages/tensorflow/contrib/learn/python/learn/estimators/estimator.py", line 439, in fit
    SKCompat(self).fit(x, y, batch_size, steps, max_steps, monitors)
  File "/usr/lib/python3.4/site-packages/tensorflow/contrib/learn/python/learn/estimators/estimator.py", line 1340, in fit
    epochs=None)
  File "/usr/lib/python3.4/site-packages/tensorflow/contrib/learn/python/learn/estimators/estimator.py", line 137, in _get_input_fn
    epochs=epochs)
  File "/usr/lib/python3.4/site-packages/tensorflow/contrib/learn/python/learn/learn_io/data_feeder.py", line 152, in setup_train_data_feeder
    x, y, n_classes, batch_size, shuffle=shuffle, epochs=epochs)
  File "/usr/lib/python3.4/site-packages/tensorflow/contrib/learn/python/learn/learn_io/data_feeder.py", line 326, in __init__
    dict([(k, check_array(v, v.dtype)) for k, v in list(y.items())]) if x_is_dict else check_array(y, y.dtype)
AttributeError: 'numpy.ndarray' object has no attribute 'items'

and the related code is:
   x_is_dict, y_is_dict = isinstance(x, dict), y is not None and isinstance(
        y, dict)
    if isinstance(y, list):
      y = np.array(y)

    self._x = dict([(k, check_array(v, v.dtype)) for k, v in list(x.items())
                   ]) if x_is_dict else check_array(x, x.dtype)
    self._y = None if y is None else \
      dict([(k, check_array(v, v.dtype)) for k, v in list(y.items())]) if x_is_dict else check_array(y, y.dtype)

the last line of the code seems wrong , it should use the y_is_dict instead of x_is_dict  ?
I change the code to :
dict([(k, check_array(v, v.dtype)) for k, v in list(y.items())]) if y_is_dict else check_array(y, y.dtype)

and then  it works .

I think the fix is correct. Created a PR #12562

@jhseu Can you close this when PR #12562 is merged?


Add Cat And Dog API to Animals

[x] My submission is formatted according to the guidelines in the contributing guide
[x] My addition is ordered alphabetically
[x] My submission has a useful description
[x] The description does not have more than 100 characters
[x] The description does not end with punctuation
[x] Each table column is padded with one space on either side
[x] I have searched the repository for any relevant issues or pull requests
[x] Any category I am creating has the minimum requirement of 3 items
[x] All changes have been squashed into a single commit

okay thanks for reviewing my PR sorry for troubling you

okay thanks for reviewing my PR sorry for troubling you

No problem ;)


how to build

Hello sir how can i build it .apt-get install acbuild not found for 14.04 ubuntu 32 bit.If possible can u give me release version for tlstun

Hi,
For linux 32bit you should be able to use the https://github.com/jsimonetti/tlstun/releases/download/v1.0/tlstun_linux_x86_v1.0.tar.bz2 version. This is a precompiled binary.
If you wish to compile it yourself, you will need a recent go toolchain and:

go get github.com/jsimonetti/tlstun
go build -o myTlsBinaryName github.com/jsimonetti/tlstun/cli/main.go

Thank you so much sir.Let me test and update results of the test

Sir how can i use it sir.Can you give me example use please


Add methods to find instruments from parameter chain

This PR adds two new methods to find instruments of specific type in a parameter chain.

@microsoft-github-policy-service agree company="Microsoft"

I'm not sure if my review comments are showing up or not, but just in case they are not, I'll copy them here.
The name of the function get_instrument_from_chain is not very descriptive and may be misleading. I would like to see something better. Possibly get_chain_link_with_instrument_of_type or get_parent_instruments_from_chain_of_type. Such naming chain to propagate to the get_sole... version as well


docs: issue template for reporting issues and requestion features

Based off suggestions from contributing guide
See: https://help.github.com/articles/about-issue-and-pull-request-templates/

:+1:
I like issue templates. I like it especially when people use them. Let's try.