Allow sending OTP for confirmation and recovery scenarios via email

Is your suggestion related to an experience ? Please describe.
Currently, confirmation and recovery scenarios via email are done by sending a link that includes a link along with a confirmation code. But there are requirements to allow users to type an OTP instead of clicking a link. Currently, it is not allowed because the confirmation code sent in the email is a UUID and it is not user-friendly to type an UUID.
Describe the improvement

A configuration to switch between OTP-based email confirmation or link-based email confirmation
Another configuration to define the format of the OTP (length and characters to be included)
An extension point to cater to more advanced customization requirements on the OTP (can extend the interface provided with https://github.com/wso2/product-is/issues/13817)
The following flows to be covered

Self-registration with email confirmation
Lock on creation/Email verification on Add user
Lite User Registration
Password Recovery
Verify on Email Update
Resend code for all of above

Only the backend implementation will be done in the first phase and end-user UIs will be implemented in another phase.

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


Why the axes and Line didn't show after rendering

Describe the error

I use the manimgl --hd OpeningManimExample.py -o, but the video's axes and plot curve didn't show? Why?
What should I do to display the axes and Curve？
Code and Error
Code:

class OpeningManimExample(Scene):
    def construct(self):
        intro_words = Text(
            """
            The original motivation for manim was to
            better illustrate mathematical functions
            as transformations.
        """
        )
        intro_words.to_edge(UP)

        self.play(Write(intro_words))
        self.wait(2)

        # Linear transform
        grid = NumberPlane((-10, 10), (-5, 5))
        matrix = [[1, 1], [0, 1]]
        linear_transform_words = VGroup(
            Text("This is what the matrix"),
            IntegerMatrix(matrix, include_background_rectangle=True),
            Text("looks like"),
        )
        linear_transform_words.arrange(RIGHT)
        linear_transform_words.to_edge(UP)
        linear_transform_words.set_stroke(BLACK, 10, background=True)

        self.play(
            ShowCreation(grid), FadeTransform(intro_words, linear_transform_words)
        )
        self.wait()
        self.play(grid.animate.apply_matrix(matrix), run_time=3)
        self.wait()

        # Complex map
        c_grid = ComplexPlane()
        moving_c_grid = c_grid.copy()
        moving_c_grid.prepare_for_nonlinear_transform()
        c_grid.set_stroke(BLUE_E, 1)
        c_grid.add_coordinate_labels(font_size=24)
        complex_map_words = TexText(
            """
            Or thinking of the plane as $\\mathds{C}$,\\\\
            this is the map $z \\rightarrow z^2$
        """
        )
        complex_map_words.to_corner(UR)
        complex_map_words.set_stroke(BLACK, 5, background=True)

        self.play(
            FadeOut(grid),
            Write(c_grid, run_time=3),
            FadeIn(moving_c_grid),
            FadeTransform(linear_transform_words, complex_map_words),
        )
        self.wait()
        self.play(
            moving_c_grid.animate.apply_complex_function(lambda z: z**2),
            run_time=6,
        )
        self.wait(2)

Error:
No Errow, but the video didn't show the axes and curve.
Environment
OS System:  Windows
manim version: v1.6.1
python version: 3.10

I encountered the same issue, but resolved by installing manim from git-hub repository.
https://github.com/3b1b/manim#directly-windows

Thank you. I will try.


fix(versions): update Activiti/example-runtime-bundle versions into master

UpdateBot pushed helm dependency: common to: 1.1.20

UpdateBot commands:
updatebot push-version --kind helm common 1.1.20


it cannot load class by ServiceLoader if set sharedUserId

When an Android app has a shared UID (User ID), it can sometimes cause issues when using ServiceLoader.load to load classes. ServiceLoader relies on the context's class loader to load the specified service class, and when using a shared UID, the class loader may not have access to the necessary resources or dependencies
try another method that is to explicitly specify the class loader to use when loading the service class:
val load = ServiceLoader.load(
ConfigRegister::class.java, ConfigRegister::class.java.classLoader
)

fix with v1.0.0 release

fix with v1.0.0 release


Links pass through the nodes

In the standard behavior, the connections goes through the node. And it can confuse the user.
Is it possible to somehow make the connections go around the nodes?

If I understand correctly, you're probably going to want to create a custom Edge type. The relevant documentation can be found here: https://reactflow.dev/docs/api/edge-types/

If I understand correctly, you're probably going to want to create a custom Edge type. The relevant documentation can be found here: https://reactflow.dev/docs/api/edge-types/

Yes, that's right. Unfortunately, when creating a custom Edge type, it only knows about the source point and target point.
Maybe there are examples when it is necessary to node as a "wall" and no connections pass through it?

Issue #1642 provides a small amount of starter code which may help with the issue you're talking about. You'd need to create a custom Edge, find the ReactFlow coordinates of two nodes, and adjust the SVG path respectively.
Here, you can see that the Bezier Path is being calculated from the positions of both nodes:
https://github.com/wbkd/react-flow/blob/56507104cfd672dbda5303003082e62f887c3f7c/src/components/Edges/BezierEdge.tsx#L19-L46

I  had the same requirement in a project so I created a custom edge and published it as a module:
https://github.com/tisoap/react-flow-smart-edge

For now this can only be done with a custom edge logic.


Error: Cannot find module './Int64'

The error Cannot find module ./Int64 came up when generating Javascript lang.
This is caused by this fragment on the spec:
              ip_number:
                type: int64
                description: IP number in long integer.

Which, as of OAG 7.6.0, doesn't generate the expected Int64 module and results in error:
    # mocha test/javascript/*.js

     Exception during run: Error: Cannot find module './Int64'
    Require stack:
    - /opt/workspace/openapi-iplocation/clients/javascript/generated/dist/model/Get200Response.js
    - /opt/workspace/openapi-iplocation/clients/javascript/generated/dist/index.js
    - /opt/workspace/openapi-iplocation/test/javascript/get.js

Until OAG handles int64 for javascript lang, ip_number type has been replaced with string https://github.com/oapicf/openapi-iplocation/commit/18e08ef0a7fd8f70435702a5e6f22993bf27e4dd .
This has been included in 1.0.0 .


The TSM storage engine

Internal people have seen the docs, external will see it soon. I haven't had a chance to refactor any of this yet, but let me have it. I'll be pushing up some refactoring changes over the weekend I think.
Will fix the merge conflicts with the stress tool in a bit, but I wanted to get people commenting on the code so I can get some feedback and fixes in.

tsdb/engine/tsm1/tsm1.go
1,904 additions, 0 deletions not shown

Anyone know what is going on here? It won't show me the file as a big green blob, so I can add comments.

Github claims a 1,500 diff limit for a file.
https://help.github.com/articles/what-are-the-limits-for-viewing-content-and-diffs-in-my-repository/#diff-limits
This seems weak.

I think Github is trying to tell us something when we commit 1500 line changes :wink:

Can we get a comment on what magicNumber is:
https://github.com/influxdb/influxdb/blob/pd-storage-engine/tsdb/engine/tsm1/tsm1.go#L78

Officially the largest PR review I've ever done :smile:.  Lot of great code in here.  Can't wait to see it merged!  Great job everyone!

Data race detection:
WARNING: DATA RACE
Read by goroutine 45:
  github.com/influxdb/influxdb/tsdb/engine/tsm1.(*Engine).nextFileName()
      /Users/benbjohnson/go/src/github.com/influxdb/influxdb/tsdb/engine/tsm1/tsm1.go:1235 +0x5a
  github.com/influxdb/influxdb/tsdb/engine/tsm1.(*Engine).rewriteFile()
      /Users/benbjohnson/go/src/github.com/influxdb/influxdb/tsdb/engine/tsm1/tsm1.go:1008 +0xdc4
  github.com/influxdb/influxdb/tsdb/engine/tsm1.(*Engine).Write.func2()
      /Users/benbjohnson/go/src/github.com/influxdb/influxdb/tsdb/engine/tsm1/tsm1.go:393 +0x48

Previous write by goroutine 46:
  github.com/influxdb/influxdb/tsdb/engine/tsm1.(*Engine).nextFileName()
      /Users/benbjohnson/go/src/github.com/influxdb/influxdb/tsdb/engine/tsm1/tsm1.go:1235 +0x7f
  github.com/influxdb/influxdb/tsdb/engine/tsm1.(*Engine).rewriteFile()
      /Users/benbjohnson/go/src/github.com/influxdb/influxdb/tsdb/engine/tsm1/tsm1.go:1008 +0xdc4
  github.com/influxdb/influxdb/tsdb/engine/tsm1.(*Engine).Write.func3()
      /Users/benbjohnson/go/src/github.com/influxdb/influxdb/tsdb/engine/tsm1/tsm1.go:402 +0x4c

Goroutine 45 (running) created at:
  github.com/influxdb/influxdb/tsdb/engine/tsm1.(*Engine).Write()
      /Users/benbjohnson/go/src/github.com/influxdb/influxdb/tsdb/engine/tsm1/tsm1.go:399 +0xd93
  github.com/influxdb/influxdb/tsdb/engine/tsm1.(*Log).flush()
      /Users/benbjohnson/go/src/github.com/influxdb/influxdb/tsdb/engine/tsm1/wal.go:576 +0xf30
  github.com/influxdb/influxdb/tsdb/engine/tsm1.(*Log).WritePoints()
      /Users/benbjohnson/go/src/github.com/influxdb/influxdb/tsdb/engine/tsm1/wal.go:244 +0x794
  github.com/influxdb/influxdb/tsdb/engine/tsm1.(*Engine).WritePoints()
      /Users/benbjohnson/go/src/github.com/influxdb/influxdb/tsdb/engine/tsm1/tsm1.go:335 +0xb0
  github.com/influxdb/influxdb/tsdb/engine/tsm1_test.TestEngine_WriteIndexQueryAcrossDataFiles()
      /Users/benbjohnson/go/src/github.com/influxdb/influxdb/tsdb/engine/tsm1/tsm1_test.go:150 +0x74b
  testing.tRunner()
      /private/var/folders/q8/bf_4b1ts2zj0l7b0p1dv36lr0000gp/T/workdir/go/src/testing/testing.go:456 +0xdc

Goroutine 46 (finished) created at:
  github.com/influxdb/influxdb/tsdb/engine/tsm1.(*Engine).Write()
      /Users/benbjohnson/go/src/github.com/influxdb/influxdb/tsdb/engine/tsm1/tsm1.go:408 +0xe48
  github.com/influxdb/influxdb/tsdb/engine/tsm1.(*Log).flush()
      /Users/benbjohnson/go/src/github.com/influxdb/influxdb/tsdb/engine/tsm1/wal.go:576 +0xf30
  github.com/influxdb/influxdb/tsdb/engine/tsm1.(*Log).WritePoints()
      /Users/benbjohnson/go/src/github.com/influxdb/influxdb/tsdb/engine/tsm1/wal.go:244 +0x794
  github.com/influxdb/influxdb/tsdb/engine/tsm1.(*Engine).WritePoints()
      /Users/benbjohnson/go/src/github.com/influxdb/influxdb/tsdb/engine/tsm1/tsm1.go:335 +0xb0
  github.com/influxdb/influxdb/tsdb/engine/tsm1_test.TestEngine_WriteIndexQueryAcrossDataFiles()
      /Users/benbjohnson/go/src/github.com/influxdb/influxdb/tsdb/engine/tsm1/tsm1_test.go:150 +0x74b
  testing.tRunner()
      /private/var/folders/q8/bf_4b1ts2zj0l7b0p1dv36lr0000gp/T/workdir/go/src/testing/testing.go:456 +0xdc

@benbjohnson race should be fixed in e3b30e3a95b859b498128e5e61c890a556834261


Installation error: inconsistent name: expected 'pytorch-tools', but metadata has 'torchtools'

(wuerstchen) ~/Developer/Wuerstchen (main u=) $ pip install -r requirements.txt
Collecting pytorch-tools@ git+https://github.com/pabloppp/pytorch-tools@master (from -r requirements.txt (line 4))
  Cloning https://github.com/pabloppp/pytorch-tools (to revision master) to /tmp/pip-install-bgmuvmb4/pytorch-tools_c07c3a635b684eafb1465faf6168efa1
  Running command git clone --filter=blob:none --quiet https://github.com/pabloppp/pytorch-tools /tmp/pip-install-bgmuvmb4/pytorch-tools_c07c3a635b684eafb1465faf6168efa1
  Resolved https://github.com/pabloppp/pytorch-tools to commit 610158d5016d6418aee27f956e7afd17ff35ba04
  Preparing metadata (setup.py) ... done
  WARNING: Generating metadata for package pytorch-tools produced metadata for project name torchtools. Fix your #egg=pytorch-tools fragments.
Discarding git+https://github.com/pabloppp/pytorch-tools@master: Requested torchtools from git+https://github.com/pabloppp/pytorch-tools@master (from -r requirements.txt (line 4)) has inconsistent name: expected 'pytorch-tools', but metadata has 'torchtools'
Collecting webdataset (from -r requirements.txt (line 1))
  Downloading webdataset-0.2.48-py3-none-any.whl (51 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 51.9/51.9 kB 7.4 MB/s eta 0:00:00
Collecting transformers (from -r requirements.txt (line 2))
  Downloading transformers-4.30.2-py3-none-any.whl (7.2 MB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 7.2/7.2 MB 49.9 MB/s eta 0:00:00
Collecting warmup_scheduler (from -r requirements.txt (line 3))
  Downloading warmup_scheduler-0.3.tar.gz (2.1 kB)
  Preparing metadata (setup.py) ... done
ERROR: Could not find a version that satisfies the requirement pytorch-tools (unavailable) (from versions: 0.1.4, 0.1.5, 0.1.7, 0.1.8, 0.1.9)
ERROR: No matching distribution found for pytorch-tools (unavailable)

I was able to get it running with the following change:
(wuerstchen) ~/Developer/Wuerstchen (main * u=) $ git diff requirements.txt
diff --git a/requirements.txt b/requirements.txt
index fb0ee12..b86346a 100644
--- a/requirements.txt
+++ b/requirements.txt
@@ -1,4 +1,4 @@
 webdataset
 transformers
 warmup_scheduler
-pytorch-tools @ git+https://github.com/pabloppp/pytorch-tools@master
+torchtools @ git+https://github.com/pabloppp/pytorch-tools@master

@dome272 we could even get rid of this dependency since you have a local copy of the Diffuzz class and we can do the same for the VectorQuantize for the vqGAN 🤔 so that would be one less thing to worry about


Add Lynx loader support

This MR adds support for the Lynx loader and the Lynx R-1 headset.
Tested features:

Head tracking :heavy_check_mark:
Hand tracking :heavy_check_mark:
I have some issues with displaying the hand model and OpenGL, need to investigate
Vulkan kind of works but is upside down and spam the console with errors

This MR is currently missing the LICENSE file.
Merging this MR should close #22

Looks good!
Can you update the CHANGES.md file, and it should be good to merge.

I've updated the CHANGES.md, feel free to merge. I am a little bit conflicted regarding the missing LICENSE file. On one hand I suppose it's important, on the other hand I can't find any LICENSE file in Lynx's tooling for Unity.

@rodolpheh Thanks!
@BastiaanOlij @akien-mga Do we have a contact at Lynx we can ping for access to their license?

Sigh, is Lynx not using the standard Khronos loader?

I've updated the CHANGES.md, feel free to merge. I am a little bit conflicted regarding the missing LICENSE file. On one hand I suppose it's important, on the other hand I can't find any LICENSE file in Lynx's tooling for Unity.

Any chance you can ping Stan Larroque on this? I don't mind nudging him on Twitter but it sounded like you guys have a more personal relationship with him?

I'll get in contact with Lynx to see if a LICENSE file is necessary. Unfortunately it seems that their loader is slightly different from Khronos' loader.

I'll get in contact with Lynx to see if a LICENSE file is necessary. Unfortunately it seems that their loader is slightly different from Khronos' loader.

Bah, alas :)

@rodolpheh
Have u tried passthrough with Lynx using Godot?
What other features YET-To-Implement for Godot on Lynx?

@rodolpheh
Mandy social reviews believe Lynx-R1 has better passthrough then e.g. Quest Pro.
It is definitely better than Pico ( One Camera non-stereo passthrough).
WHY the priority to show Godot supports the Lynx-R1 passthrough with clear RECENT (less than 6 months old) improvement in color calibration and background color video alignment of the Lynx TWO stereo color camera!

Just to close this topic, I haven't tried the passthrough on the Quest Pro but I've tried it on Lynx and the Pico 4. Stereo camera really improves the experience and gives depth perception which is priceless. A simple test I tried which I think is very much telling about the comfort and quality of passthrough is to juggle with the headset on my head, and it is possible to juggle while wearing the Lynx (impossible on Pico 4 due to lack of depth perception).

@rodolpheh can you get in touch with me about the loader situation? I'd like to follow up with the vendor as well as the WG because my understanding is that we have solved most of the blockers to adoption of the generic loader, but I don't have a Lynx contact. My email is my handle at collabora dot com.

To ALL,
This discussion is about making Lynx R1 SDK available for Godot developers.
Citing how Lynx R1's passthrough has potential advantages over others is strictly my personal opinion. I am not here to change anyone's opinion against other headsets. I just hope for "full support" of Lynx in Godot.

@GeorgeS2019 We can't embed Lynx R1 proprietary logic into an Open Source project like Godot, this is one of the reasons this loader plugin is not part of the core repository and why I express my frustration that there are more vendors who are creating their own non-standard loaders on Android, than there are vendors who fully support Khronos' Open Source loader that is part of the OpenXR spec.
If the only option for pass through on Lynx is to use a proprietary SDK, than this logic needs to be implemented as a separate plugin, I really hope they are not going down this path because its a royal PITA to do.
OpenXR has a standard for supporting AR solutions as implemented by MS and as far as I am aware Magic Leap that involves setting the correct blend mode on the provided image, Godot fully supports this.
OpenXR also has a vendor extension by Meta for pass through that could be adopted by Lynx though I hope OpenXR soon adds a core extension for pass through all vendors can adhere to so we as a game engine developer don't need to implement a plethora of different solutions.
In the end, this is up to the hardware vendors to do properly, to adopt and support the standard and join in with the discussions the OpenXR working group is having, instead of re-inventing the wheel and making it harder for a FOSS engine like Godot to support them.
Disclaimer here, I don't have a Lynx R1, I've not looked at their SDK, I'm basing my opinion here on the discussion above. For all I know Lynx is taking all the right steps but just need to have a little guidance to ensure conformity to the standard, so indeed @rodolpheh if you could get @rpavlik in touch with the right people at Lynx that would be awesome.

Hey @rodolpheh

Hand tracking seems to work but there is rendering issues preventing them from showing.

Be sure to report this on the Godot issue tracker. Clay and myself are currently investigating an issue where on AMD hardware we're having geometry not rendering correctly when multiview is enabled, though this was on Vulkan, not OpenGL. Still the cause may be similar.

They do show with Vulkan but Vulkan display is upside down. Let me know if you're aware of any feature I should check for.

I'm not aware of anything in the OpenXR spec where we can communicate the orientation of the image we're submitting, this would seem to be an issue on the Lynx itself where they are expecting an orientation other then is standard.

Just to close this topic, I haven't tried the passthrough on the Quest Pro but I've tried it on Lynx and the Pico 4. Stereo camera really improves the experience and gives depth perception which is priceless. A simple test I tried which I think is very much telling about the comfort and quality of passthrough is to juggle with the headset on my head, and it is possible to juggle while wearing the Lynx (impossible on Pico 4 due to lack of depth perception).

Ah that explains why the PICO doesn't have the same sort of distortion the Quest 2 has when attempting re-projection of the stereo image. I also haven't tried the Quest Pro so can't comment on that.
For the use case of picking up your controllers and drawing your boundary I didn't feel the lack of depth perception was an issue, but I can see that it would be for more proper AR experiences.

FYI @rodolpheh, for proprietary extensions (like the scene capture extension of Meta Quest devices) we (mostly my colleague @konczg) created a PR that allows such OpenXR extensions packaged as GDExtensions: https://github.com/godotengine/godot/pull/68259
It is mostly reviewed already by @BastiaanOlij and @m4gr3d, we just need to rebase it to the current master. We will see if we can do that in the next few days, our work on this has been preempted by other projects in the last few weeks.
This solution could be used to support the Lynx passthrough API in Godot as well.

As far as I can tell, Lynx's tooling for Unity sets the XrEnvironmentBlendMode to be Alpha blend or Opaque to enable or disable AR passthrough. It should be using standard OpenXR feature if I'm not mistaken. I am not able to try it now as I am pretty busy but will try to come back quickly with something.
Please keep in mind I'm still in the process of learning about Godot and OpenXR.
@BastiaanOlij I'll try to capture more precisely the issue with the rendering and report it to the main Godot repository. It doesn't seem to happen on Vulkan but Vulkan has other issues.
I understand your frustration regarding the proliferation of different OpenXR loader (and sometimes the lack of distribution of them, or the inaccessibility of them).
As for depth perception, I do believe it's important for AR experience, specially when using hands as the main controllers and interacting with virtual object with direct touch (as opposed to far field interaction e.g. laser pointer).
@rpavlik I'll get in touch with you and see if I can arrange some introductions.

Need more investigation but I'm struggling to find how to enable passthrough. Checking if AR or passthrough is supported in Godot returns false. I'll probably need more time to figure this out and I think it'd be better to create an issue to track the efforts into this. I can see that the blend modes are detected according to these lines and they are the ones expected for the Lynx:
02-23 17:55:23.923  4554  4611 I godot   : OpenXR: Found environmental blend mode XR_ENVIRONMENT_BLEND_MODE_OPAQUE
02-23 17:55:23.923  4554  4611 I godot   : OpenXR: Found environmental blend mode XR_ENVIRONMENT_BLEND_MODE_ALPHA_BLEND

Regarding the OpenXR runtime, on start of my application I have this line showing up:
02-23 17:55:23.923  4554  4611 I godot   : OpenXR: Running on OpenXR runtime:  Snapdragon OpenXR 'v1.6.1' based on Monado(XRT) by Collabora   13.1.1

@rpavlik would this message explains why their OpenXR runtime doesn't work with KHR's loader?
@BastiaanOlij regarding the OpenGL issue, this is the error I get. Just checking if you've seen it before or if it is the one you're investigating. If not I'll open a ticket on Godot's repository:
02-23 17:55:52.261  4554  4611 E godot   : USER ERROR: GL ERROR: Source: OpenGL	Type: Error	ID:<PHONE_NUMBER>	Severity: High	Message: Mismatch between shader number of views and FBO number of views
02-23 17:55:52.261  4554  4611 E godot   :    at: _gl_debug_print (drivers/gles3/rasterizer_gles3.cpp:167)

Double checking the logs, I see that there may be an issue with the version of OpenGL requested:
02-23 17:55:24.068  4554  4611 I godot   : OpenXR: Requested OpenGL version exceeds the maximum version this runtime has been tested on and is known to support.
02-23 17:55:24.068  4554  4611 I godot   : - desired_version  3.3.0
02-23 17:55:24.068  4554  4611 I godot   : - minApiVersionSupported  2.0.0
02-23 17:55:24.068  4554  4611 I godot   : - maxApiVersionSupported  3.2.1023

Hey @rodolpheh

As far as I can tell, Lynx's tooling for Unity sets the XrEnvironmentBlendMode to be Alpha blend or Opaque to enable or disable AR passthrough. It should be using standard OpenXR feature if I'm not mistaken. I am not able to try it now as I am pretty busy but will try to come back quickly with something.
Please keep in mind I'm still in the process of learning about Godot and OpenXR.

Indeed, for me similarly, I don't know enough about the Lynx and where it differs. This actually should really cool, from what I understand from the OpenXR specs setting the blend mode to alpha is what you should be doing on AR devices, and i think it's kind of inferred that on passthrough this should enable the pass through.
Quest is the odd ball out here, I guess in part because Meta had their existing VrApi solution they needed to make available in OpenXR but also because Quest offers a bunch more options with how passthrough is applied.
It's kind of counter intuitive for Godot now because we have a passthrough mode that you don't need for passthrough on several devices :)

Need more investigation but I'm struggling to find how to enable passthrough. Checking if AR or passthrough is supported in Godot returns false. I'll probably need more time to figure this out and I think it'd be better to create an issue to track the efforts into this.

Like I said above, the passthrough extension is a Meta thing, nice and confusing if Lynx just uses the blend mode.

I can see that the blend modes are detected according to these lines and they are the ones expected for the Lynx:

There should be a property on the OpenXRInterface to change the blend mode. So you should be able to do something like:
func _ready():
  var xr_interface : OpenXRInterface = XRServer.find_interface("OpenXR")
  if xr_interface and xr_interface.is_initialized():
    get_viewport().use_xr = true
    xr_interface.set_environment_blend_mode(XR_ENV_BLEND_MODE_ALPHA_BLEND)

@rpavlik would this message explains why their OpenXR runtime doesn't work with KHR's loader?

Ah! Ryan was talking about that yesterday, yes if they are using the Snapdragon OpenXR loader that would explain it.
So basically the Lynx entry in loaders really is the Snapdragon entry as it would theoretically support any Snapdragon based HMD.

Double checking the logs, I see that there may be an issue with the version of OpenGL requested:
This can be mostly ignored, the official stance as I understand is that we need to at least support the minimum, and that the maximum is sort of a "things are likely downwards compatible but up to you to test".
On desktop it's annoying because most OpenXR runtimes report a minimum of OpenGL 4.0.0, while Godot is a GLES3 renderer and thus uses a 3.3 context. Hasn't given us problems yet (other than possibly some annoying issues with linear v.s. sRGB).

@BastiaanOlij I've already had set up the blend mode. Here is my current function to initialize OpenXR:
func _ready():
	interface = XRServer.find_interface("OpenXR")
	if interface and interface.is_initialized():
		print("OpenXR initialised successfully")
		var modes = interface.get_supported_environment_blend_modes()

		for mode in modes:
			print(env_mode_to_str(mode))

		get_viewport().use_xr = true
		interface.set_environment_blend_mode(XRInterface.XR_ENV_BLEND_MODE_ALPHA_BLEND)
	else:
		print("OpenXR not initialised, please check if your headset is connected")

I might be missing something on the scene side. I've set up the environment background to either Clear Color or Custom Color with an alpha of 0, to no effect.

@rodolpheh DUH!
Yeah just add this:
get_viewport().transparent_bg = true

That's needed to ensure the background has a proper alpha channel and it disables most of the background code.
I think that will do the trick fingers crossed.

Yes alpha environment blend mode is how you do video pass thru (and possibly some optical pass thru with dimmers) in the standard. Additive is for "normal" optical pass thru where you can add light but not remove it (black is transparent). Some vendors have added extensions for fancier video see thru, but (at least in my opinion) those should be in addition to the standard blend mode. Hopefully Meta will agree at some point, I know the engineers have heard about it.

Seems so close but I might be missing something. At first launch, it doesn't switch to passthrough, but there is a very small moment where the view goes black for one frame (could be the switch to the alpha blend mode ?). If I relaunch the app from Godot (while it is running), it will show one frame from the RGB camera then freeze completely and displays the following:
OpenVR Head pose now tracking with high confidence
OpenXR: failed to release swapchain image! [ XR_ERROR_INSTANCE_LOST ]
OpenXR: failed to end frame! [ XR_ERROR_LAYER_INVALID ]
OpenXR head space location not valid (check tracking?)
OpenXR: xrWaitFrame() was not successful [ XR_ERROR_INSTANCE_LOST ]
OpenXR: failed to end frame! [ XR_ERROR_TIME_INVALID ]

It also happens if I switch between applications and go back to the Godot application. One frame from the passthrough is shown before it freezes completely, showing the above in the logs.

I really want to thank everybody working on this and I hope my question isn't a stupid one but here goes: What versions of Godot will I be able build VR apps for Lynx on?
Will this work on Godot 3 or is it going to only work in Godot 4?

@rodolpheh Glad they're addressing the issue for passthrough!
Can you start a separate issue / thread for it. This will allow us to better track ongoing issues and their status.


Bumps to Uno 4.0 Preview

Description of Change
This change bumps Uno to 4.0 preview bits, which include binary breaking changes.
Bugs Fixed
None

Related to issue #

API Changes
None
Behavioral Changes
Nonoe.
PR Checklist

[ ] Has tests (if omitted, state reason in description)
[x] Rebased on top of main at time of PR
[x] Changes adhere to coding standard
[ ] Updated documentation

@mattleibow I assume the build errors are caused by the inclusion of nuget.org in the nuget.config file, though I'm not able to build locally as nuget.org packages are missing. What's the correct route to fix this ? Thanks!

@jeromelaban @mattleibow This is an important issue as without it fixed Skia cannot be used with Uno Platform (UWP projects).
On my end attempting to construct an SKXamlCanvas with Skia preview version 2.88.0-preview.155 (SkiaSharp & SkiaSharp.Views.Uno) throws the exception:
{System.TypeLoadException: Could not resolve type with token 0100007b from typeref (expected class 'Windows.UI.Core.UIAsyncOperation' in assembly 'Uno, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null')
at System.Runtime.CompilerServices.AsyncVoidMethodBuilder.Start[TStateMachine] (TStateMachine& stateMachine) [0x0002c] in /Users/builder/jenkins/workspace/archive-mono/2020-02/android/release/mcs/class/referencesource/mscorlib/system/runtime/compilerservices/AsyncMethodBuilder.cs:84
at SkiaSharp.Views.UWP.SKXamlCanvas.Invalidate () [0x00007] in :0
at SkiaSharp.Views.UWP.SKXamlCanvas.OnDpiChanged (Windows.Graphics.Display.DisplayInformation sender, System.Object args) [0x00013] in D:\a\1\s\source\SkiaSharp.Views.Uno\SkiaSharp.Views.Uno\SKXamlCanvas.cs:83
at SkiaSharp.Views.UWP.SKXamlCanvas.Initialize () [0x0000e] in D:\a\1\s\source\SkiaSharp.Views.Uno\SkiaSharp.Views.Uno\SKXamlCanvas.cs:36
at SkiaSharp.Views.UWP.SKXamlCanvas..ctor () [0x00027] in D:\a\1\s\source\SkiaSharp.Views.Uno\SkiaSharp.Views.Uno.Android\SKXamlCanvas.Android.cs:14
at FinancialManager.UWP.Controls.LineChart..ctor () [0x00177] in ...\Source\Controls\Charts\LineChart\LineChart.cs:108 }

Is there any timeframe for this patch being applied and pushed to nuget? Possibly applied against 2.80.3 and published as a minor update of that if 2.88 isn't likely to be ready for release soon?
I've been tinkering with a replacement for my use of SkiaSharp and I'm almost at the point where I need to decide if I'm going to commit to that. Knowing the expected timeframe for this would help me greatly. Thanks!

This corresponds with the SkiaSharp 2.88.0-preview.179 nuget (including SkiaSharp.Views and SkiaSharp.Views.Uno)
Any Uno version < 4.0 must use SkiaSharp < 2.88.0-preview.179 and
Any Uno version >= 4.0 must use SkiaSharp >= 2.88.0-preview.179


For a Pandas Serie containing NaN, Spyder IPython console is "flud" by error message

let's assume mySerie is containing a NaN value.
When I type "mySerie.to_csv(" then the following error message is written at the prompt, forbidding me to write any further.
I guess the "mySerie" is getting somehow evaluated by the Help or the auto-completion.
I tried to disable the automatic Help, it did not change anything
Reproducing the problem
in IPython console, execute this line :
import pandas as pd mySerie = pd.Series([1,2,3]).diff()
execution "mySerie" result to this output :
C:\Program Files\WinPython-64bit-<IP_ADDRESS>\python-3.4.4.amd64\lib\site-packages\pandas\core\format.py:2087: RuntimeWarning: invalid value encountered in greater   has_large_values = (abs_vals > 1e8).any() C:\Program Files\WinPython-64bit-<IP_ADDRESS>\python-3.4.4.amd64\lib\site-packages\pandas\core\format.py:2088: RuntimeWarning: invalid value encountered in less   has_small_values = ((abs_vals < 10 ** (-self.digits)) & C:\Program Files\WinPython-64bit-<IP_ADDRESS>\python-3.4.4.amd64\lib\site-packages\pandas\core\format.py:2089: RuntimeWarning: invalid value encountered in greater   (abs_vals > 0)).any() Out[74]:  0   NaN 1     1 2     1 dtype: float64
typing (without executing) mySerie.to_csv( will trigger the same error message. It is hard to write a complete command due to this.
Versions and main components
I installed WinPython-64bit-<IP_ADDRESS> which is officially including :

Spyder Version:
spyder3.0b4+  (but it is still frustrating to see only 3.0.0dev in the About dialog)
Python Version:
3.4.4 64 bits
Operating system:
Win 7, 64bit

Dependencies
IPython >=3.0      :  4.1.1 (OK)
jedi >=0.8.1;<0.9.0:  0.9.0 (NOK)   <== possible source of problem  ?
matplotlib >=1.0   :  1.5.1 (OK)
numpy >=1.7        :  1.10.4 (OK)
pandas >=0.13.1    :  0.17.1 (OK)
pep8 >=0.6         :  1.7.0 (OK)
pyflakes >=0.6.0   :  0.9.2 (OK)
pygments >=1.6     :  2.1 (OK)
pylint >=0.25      :  1.5.4 (OK)
qtconsole >=4.0    :  4.1.1 (OK)
rope >=0.9.4       :  0.9.4-1 (OK)
sphinx >=0.6.6     :  1.3.5 (OK)
sympy >=0.7.3      :  <IP_ADDRESS> (OK)
zmq >=13.0.0       :  15.2.0 (OK)

This was fixed in Spyder 2.3.9 and it's also fixed in Spdyer 3.0, please update :-)


Filter regenerator-runtime messages in error stack

\cc @inikulin @AlexanderMoskovkin

lgtm

@AlexanderMoskovkin Once functional tests pass - it's good to merge, also it's currently blocking for all other PRs

lgtm


Game Crashes in Release Mode giving logs from previous versions

Godot 3.2.3 (tried on all release versions until 3.1 reimporting etc)
GLES2 Windows 10
The game runs fine in debug mode but crashes  in release mode after few interactions giving strange log that I written long time ago,
what could be happening and how can I avoid this?

It seems related to queue_free, I used all possible checks and now it works with 'is_instance_valid' and 'is_queued_for_deletion'
I think it is strange that it worked on debug mode and not release mode.

That's a bug in 3.2.3, if you use 3.2.4 RC 3 the debug mode should raise errors about those.


Issue with yield self within a ternary operator

After your NoRuKo talk I tested against our codebase and this issue was immediately obvious.

Ruby version: ruby 2.6.6p146 (2020-03-31 revision 67876) [x86_64-darwin19]
Rubyfmt git sha: 3435618

Input file
def foo(&block)
  block_given? ? yield(self) : self
end

Rubyfmt's output
def foo(&block)
  block_given? ? yield self : self
end

This breaks because
Output is syntactically incorrect, Ruby errors with syntax error, unexpected self, expecting ':'.

Bump - this is the only bug we're seeing on our few thousand files at CharlieHR 😄
@penelopezone I'd love to be able to submit a pull request for this bug, ideally with a test. Could you point me in the direction of the files I should start from? It looks like I'd want to add a fixtures/small/yield_with_ternery_hook.rb and then update something in librubyfmt/src/format.rs? How do I actually run the tests?

Hi there! Generally, I would ask you to please not bump issues for bumping's sake. I track them all and I work through them in the order that makes sense to me. I'll get to it eventually, I promise :)
As for working on it: I would suggest adding a new fixture, and running the tests with ./script/tests/text_fixtures.sh. You will need both _expected and _actual files. In order to actually fix it you'll probably need to add a formatting context: https://github.com/penelopezone/rubyfmt/blob/trunk/librubyfmt/src/parser_state.rs#L15 called "IfOp' (IfOp is what ruby calls a ternary) and then add that call here: https://github.com/penelopezone/rubyfmt/blob/trunk/librubyfmt/src/format.rs#L2429. Once you've done that, checking the current formatting context: https://github.com/penelopezone/rubyfmt/blob/trunk/librubyfmt/src/parser_state.rs#L442 and forcing parens in a yield call: https://github.com/penelopezone/rubyfmt/blob/trunk/librubyfmt/src/format.rs#L2509 should work.
I hope that helps.

Generally, I would ask you to please not bump issues for bumping's sake.

Ack, sorry Penelope! Thanks for letting me know, I won’t do it again. (Also sorry for replying on Twitter first, I checked Twitter before checking my email 😅)

As for working on it: …

Amazing, I’ll give it a go 😄 Thanks for the tip about IfOp, I definitely would’ve been tripped up by that.


Add Markdownlint and fix all markdown

Add hack/markdownlint.sh and fix all linter warnings for all markdown files in the repository to have a solid baseline for enabling linter as check.

Squashed all fixes into one. Left the linter addition to a separate one.

/lgtm


Unable to find any devices for spec /device:GPU:0 [Op:__inference__train_body_2028]

ddpg code run:
07:44:34.818 [INFO] (trainer.py:105) Total Epi:    44 Steps:    8800 Episode Steps:   200 Return: -1098.1678 FPS: 6714.39
07:44:34.849 [INFO] (trainer.py:105) Total Epi:    45 Steps:    9000 Episode Steps:   200 Return: -1082.6376 FPS: 7052.35
07:44:34.896 [INFO] (trainer.py:105) Total Epi:    46 Steps:    9200 Episode Steps:   200 Return: -1451.9158 FPS: 4320.54
07:44:34.941 [INFO] (trainer.py:105) Total Epi:    47 Steps:    9400 Episode Steps:   200 Return: -1390.2553 FPS: 4567.13
07:44:34.987 [INFO] (trainer.py:105) Total Epi:    48 Steps:    9600 Episode Steps:   200 Return: -1171.9928 FPS: 4364.63
07:44:35.031 [INFO] (trainer.py:105) Total Epi:    49 Steps:    9800 Episode Steps:   200 Return: -1178.7816 FPS: 4601.59
07:44:35.074 [INFO] (trainer.py:105) Total Epi:    50 Steps:   10000 Episode Steps:   200 Return: -1347.0888 FPS: 4847.24
Traceback (most recent call last):
File "/home/serlon/Documents/Code/V2-DDPG-LTC/demo.py", line 27, in
trainer()
File "/home/serlon/anaconda3/envs/tf/lib/python3.6/site-packages/tf2rl/experiments/trainer.py", line 122, in call
None if not self._use_prioritized_rb else samples["weights"])
File "/home/serlon/anaconda3/envs/tf/lib/python3.6/site-packages/tf2rl/algos/ddpg.py", line 119, in train
states, actions, next_states, rewards, done, weights)
File "/home/serlon/anaconda3/envs/tf/lib/python3.6/site-packages/tensorflow_core/python/eager/def_function.py", line 457, in call
result = self._call(*args, **kwds)
File "/home/serlon/anaconda3/envs/tf/lib/python3.6/site-packages/tensorflow_core/python/eager/def_function.py", line 520, in _call
return self._stateless_fn(*args, **kwds)
File "/home/serlon/anaconda3/envs/tf/lib/python3.6/site-packages/tensorflow_core/python/eager/function.py", line 1823, in call
return graph_function._filtered_call(args, kwargs)  # pylint: disable=protected-access
File "/home/serlon/anaconda3/envs/tf/lib/python3.6/site-packages/tensorflow_core/python/eager/function.py", line 1141, in _filtered_call
self.captured_inputs)
File "/home/serlon/anaconda3/envs/tf/lib/python3.6/site-packages/tensorflow_core/python/eager/function.py", line 1224, in _call_flat
ctx, args, cancellation_manager=cancellation_manager)
File "/home/serlon/anaconda3/envs/tf/lib/python3.6/site-packages/tensorflow_core/python/eager/function.py", line 511, in call
ctx=ctx)
File "/home/serlon/anaconda3/envs/tf/lib/python3.6/site-packages/tensorflow_core/python/eager/execute.py", line 67, in quick_execute
six.raise_from(core._status_to_exception(e.code, message), None)
File "", line 3, in raise_from
tensorflow.python.framework.errors_impl.InvalidArgumentError: Unable to find any devices for spec /device:GPU:0 [Op:__inference__train_body_2028]
how?I have installed driver
I had try cuda-10.0 cuda-10.1,cuda-10.2 ,it's same error

Hi @tanjhysj0, thanks for the report.
Which TensorFlow version are you using?

@ tanjhysj0，您好，感谢您的举报。
您正在使用哪个TensorFlow版本？

I had try 2.0 and 2.1 ,same problem

Sorry for late reply.
Can you try to run with CPU (instead of GPUs) by specifying --gpu -1 on command line? This clarifies whether the error comes from GPUs or not.
According to your error message, it seems you can try that with following command:
$ python /home/serlon/Documents/Code/V2-DDPG-LTC/demo.py --gpu -1

If you will still encounter some errors, then it would be helpful if you can provide the full codes of your /home/serlon/Documents/Code/V2-DDPG-LTC/demo.py.

I close this issue. If you have encountered the same issue, then please open this again.


gnome/eog: add jxl support

Description of changes
should after https://github.com/NixOS/nixpkgs/pull/299988
add jxl support for gnome and eog, closed #197005
Testing on gnome(wayland)

[ ] thumbnails in nautilus works
[ ] setting jxl wallpaper by settings works
[ ] setting jxl wallpaper by context menu works
[ ] opening jxl using eog works

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Priorities
Add a :+1: reaction to pull requests you find important.

Due to this issue, some .jxl images are not are not thumbnailed correctly. upstream fixed this in https://github.com/libjxl/libjxl/pull/3218 and here the update pr https://github.com/NixOS/nixpkgs/pull/288419 (Idk why it hasn't been backported)
Other things seem to work fine

I think we can accept fixes making it in a later staging cycle. Thanks for keeping track of this.


[Issue]: Not seeing GPU sampling values (busy, power, temp, etc.) with high GPU counts

Problem Description
When running a Fortran code, for example on 16 GPUs, I can see in the traces the GPU sampling values: GPU Busy, GPU Memory, Power, etc. However, if I run the same code on 512 MI250Xs then those metrics disappear from the trace, I only get the HIP streams/queues. I'm using the same cfg file and the same running command, the only thing I change is the number of GPUs.
Operating System
SLES 15-SP5
CPU
AMD EPYC 7A53 64-Core Processor
GPU
AMD Instinct MI250X
ROCm Version
ROCm 6.0.0
ROCm Component
No response
Steps to Reproduce
No response
(Optional for Linux users) Output of /opt/rocm/bin/rocminfo --support
No response
Additional Information
In the cfg file I have:
OMNITRACE_USE_PROCESS_SAMPLING                     = true
OMNITRACE_USE_ROCM_SMI                             = true
OMNITRACE_SAMPLING_CPUS                            = none
OMNITRACE_SAMPLING_GPUS                            = all
I have also tried changing the sampling GPUs to a few ones instead of all, just in case, but it didn't work either.

Hi @xaguilar. Internal ticket has been created to investigate your issue. Thanks!


Feature Requests: Multipage Layout

An option to add borders around each page would be helpful.
An option to set the output size would be great. For example, legal, 11x17, or 13x19 would make the output more useable, especially at the higher pages per sheet values.
An option to enable or disable debugging error messages:

Also, once this error is dismissed, clicking on Submit without adding a file causes the page to become unusable as the button permanently changes to "Processing..." until the page is reloaded.

Can you make these seperate tickets sorry, hard to track each one
For
An option to set the output size would be great. For example, legal, 11x17, or 13x19 would make the output more useable, especially at the higher pages per sheet values.
Is this output size of the final document?

An option to add borders around each page would be helpful. addded in 0.14.4


MIC-688: UaR: Close CSIP

Codecov Report
Attention: Patch coverage is 89.28571% with 3 lines in your changes missing coverage. Please review.

Project coverage is 88.74%. Comparing base (5e1a3b0) to head (94b629b).

Files with missing lines
Patch %
Lines

...outes/journeys/update-review/details/controller.ts
40.00%
3 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #293      +/-   ##
==========================================
- Coverage   91.87%   88.74%   -3.14%
==========================================
  Files         336      338       +2
  Lines        4962     4985      +23
  Branches      753      755       +2
==========================================
- Hits         4559     4424     -135
- Misses        399      552     +153
- Partials        4        9       +5

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


consider duck typing for jnp.ones_like, other similar functions

right now, jnp.ones_like(jax.ShapeDtypeStruct(shape=(1, 2, 3), dtype=jnp.float32) throws a type error
it probably shouldn't, and in fact jnp.ones_like should probably work on anything that has shape, dtype, etc attributes

jnp.ones_like et al would ideally get shape, dtype, etc from x whatever x is and only check that the shape, dtype, etc are themselves well typed

Seems reasonable! (In fact I vaguely recall this coming up before...)
What do you think, @jakevdp ?

Sure, sounds reasonable to me. We have to be somewhat careful because some valid inputs won't have a dtype or shape defined (e.g. Python scalars) and some non-array inputs we want to be errors (e.g. lists and tuples).

Maybe we can try to look for shape and dtype attributes first, and if that fails fall back to the current path.

I just ran into a case where this would be nice as well. Would it be possible for me to make a PR for this or are there non-obvious things that could get broken?

@davisyoshida thanks for the ping and the offer! Looks like @jakevdp got it in #16265 though.

Someday I hope to fix an issue or even just answer a stackoverflow question before he gets to it!


Minor changes of docs/en/user-guide/dynamic-tables/resharding.md

I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=en
Please, consider these corrections as suggestions and feel free to change them without any explanation.

By the way, are you interested in such kind of improvements? Maybe it's more time-consuming than profitable, so I won't send such minor changes and try to batch them (or won't send them at all).


Assets namespace is missing from Google.AR.Sceneform.Namespace

Looking at the transform here:
https://github.com/xamarin/XamarinComponents/blob/master/Android/SceneForm/source/Assets/Transforms/Metadata.xml
<metadata>
     <attr<EMAIL_ADDRESS>name="managedName">Google.AR.Sceneform.Assets</attr>

    <attr path="/api/package[@name='com.google.ar.sceneform.assets']/class[@name='RenderableSource']/method[@name='call' and count(parameter)=0]" name="return">Java.Lang.Object</attr>

</metadata>

I would assume that I could find the RenderableSource class inside the Google.AR.Sceneform.Assets namespace, but after adding the Xamarin.Android.Sceneform.Assets nuget preview package I do not see the Assets namespace in the Google.AR.Sceneform namespace, hence the RenderableSource class is not available.
Looking inside the Xamarin.Android.Sceneform.Assets.dll assembly, the top level namespace is Com.Google.Sceneform_assets, and there is only a D class inside:

I also wonder why the package names use Xamarin.Android.XX, while ARCore uses Xamarin.Google.ARCore, etc. Since they are related it seems to me that all packages should start with Xamarin.Google rather than Xamarin.Android? Might make them all easier to find, but that is another issue.

I need to use this class and i have the same problem, please fix it!

@craigktreasure, you have done a great job with other issue, can you also solve this so we have all component for arcore?
Thanks!!!

I don't know. I'll have to see what I have time for next week. I've burnt all of my extra curricular time this week I'm afraid.


how to use in .tsx   this.fileName && this.imageRef does not exist

when I try .js file evething is OK. but I change to .tsx file this.fileName && this.imageRef throw Error and not use useRef :(

you need to declare this variable within class.
export class ThumbnailDialogContent extends React.Component<IThumbnailDialogContentProps, IThumbnailDialogContentState> {
imageRef = "";
fileUrl ="";
.
.
.}

Hi I’m not sure what you are referring to, there is nothing about
thumbnails or dialogs in this code?
On Wed, 18 Dec 2019 at 14:55, siva2502<EMAIL_ADDRESS>wrote:

you need to declare this variable within class.
export class ThumbnailDialogContent extends
React.Component<IThumbnailDialogContentProps, IThumbnailDialogContentState>
{
imageRef = "";
fileUrl ="";
.
.
.}
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/DominicTobias/react-image-crop/issues/320?email_source=notifications&email_token=AAFZT6SWXOF6SSP5AEFT6BDQZHCO7A5CNFSM4JNFYZMKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHFB5BA#issuecomment-566894212,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFZT6Q7JAU5SK2WCTHMJLDQZHCO7ANCNFSM4JNFYZMA
.


Add Proxy of /graphql over to rails application

Pretty simple, just proxying a POST /graphql request over to the rails side.
# TODO:

[x] initial proxying
[x] store rails URL in ENV

Closing in favor of #185


docs(buttons): Improve docs for Buttons element page

Rephrase sentences and change structure for several blocks.
Create .button-full class and add pointer-events: none to .disabled class.

Codecov Report

Merging #210 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##           master   #210   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files          20     20
  Lines         379    379
=====================================
  Hits          379    379

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 129329e...5f0bf8a. Read the comment docs.


[Ironsworn] [Fix] Remove autocheck on health and spirit.

Changes / Comments
A small fix for health and spirit checks. They were automatically setting debilities but that was incorrect behaviour.
Roll20 Requests
Comments are very helpful for reviewing the code changes. Please answer the relevant questions below in your comment.

[x] Does the pull request title have the sheet name(s)? Include each sheet name.
[x] Is this a bug fix?
[ ] Does this add functional enhancements (new features or extending existing features) ?
[ ] Does this add or change functional aesthetics (such as layout or color scheme) ?
[ ] If changing or removing attributes, what steps have you taken, if any, to preserve player data ?
[ ] If this is a new sheet, did you follow Building Character Sheets standards ?

:+1: This is a good fix, since the player has to roll a miss when the track is at zero to get the respective debility -- going to zero by itself isn't enough to get a debility. (as described in pages 91 and 95 of the freely available rulebook PDF)


Add thelounge to list of clients

Signed-off-by: Danny Abukalam<EMAIL_ADDRESS>

This introduction to clients offers a deliberately incomplete list. It serves only as a starting point for getting users onto IRC.

Thanks for the PR, but the client guide is meant for first-time IRC users, so clients like TL aren't for the target audience.


refactor: move cache logic into the factory

:+1:  Still not as clean as I'd like but nice improvement.


Binary (unicode) replacements will crash mitmproxy

Steps to reproduce the problem:

Add a regex replacement for responses (~s) with the regex containing unicode characters (for instance, '\u0020\u1200\u1234'). The replacement can be anything. Note how mitmproxy changes all the '\' to a double one, thinking it is matching the '\' itself.
If mitmproxy receives a response, it will crash with the message: 'bad escape \u at position 0'

Any other comments? What have you tried so far?
I have also tried to replace binary data by using '\x20\x12\x00\x12\x34'. This will also crash the application, although with a different error message.
System information
Mitmproxy version: 2.0.2 (release version)
Python version: 3.6.3
Platform: Linux-4.9.0-kali3-amd64-x86_64-with-Kali-kali-rolling-kali-rolling
SSL version: OpenSSL 1.1.0g  2 Nov 2017
Linux distro: Kali kali-rolling kali-rolling
Complete stack trace for using '\u0123' as replacement.
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/mitmproxy/tools/console/master.py", line 281, in run
self.loop.run()
File "/usr/lib/python3/dist-packages/urwid/main_loop.py", line 278, in run
self._run()
File "/usr/lib/python3/dist-packages/urwid/main_loop.py", line 376, in _run
self.event_loop.run()
File "/usr/lib/python3/dist-packages/urwid/main_loop.py", line 682, in run
self._loop()
File "/usr/lib/python3/dist-packages/urwid/main_loop.py", line 715, in _loop
alarm_callback()
File "/usr/lib/python3/dist-packages/urwid/main_loop.py", line 164, in cb
callback(self, user_data)
File "/usr/lib/python3/dist-packages/mitmproxy/tools/console/master.py", line 239, in ticker
changed = self.tick(timeout=0)
File "/usr/lib/python3/dist-packages/mitmproxy/master.py", line 109, in tick
handle_func(obj)
File "/usr/lib/python3/dist-packages/mitmproxy/controller.py", line 70, in wrapper
master.addons(f.name, message)
File "/usr/lib/python3/dist-packages/mitmproxy/addonmanager.py", line 90, in call
self.invoke(i, name, *args, **kwargs)
File "/usr/lib/python3/dist-packages/mitmproxy/addonmanager.py", line 85, in invoke
func(*args, **kwargs)
File "/usr/lib/python3/dist-packages/mitmproxy/addons/replace.py", line 93, in response
self.execute(flow)
File "/usr/lib/python3/dist-packages/mitmproxy/addons/replace.py", line 83, in execute
self.replace(f.response, rex, s)
File "/usr/lib/python3/dist-packages/mitmproxy/addons/replace.py", line 100, in replace
obj.replace(rex, s, flags=re.DOTALL)
File "/usr/lib/python3/dist-packages/mitmproxy/net/http/message.py", line 263, in replace
pattern, repl, self.content, flags=flags, count=count
File "/usr/lib/python3.6/re.py", line 202, in subn
return _compile(pattern, flags).subn(repl, string, count)
File "/usr/lib/python3.6/re.py", line 301, in _compile
p = sre_compile.compile(pattern, flags)
File "/usr/lib/python3.6/sre_compile.py", line 562, in compile
p = sre_parse.parse(p, flags)
File "/usr/lib/python3.6/sre_parse.py", line 855, in parse
p = _parse_sub(source, pattern, flags & SRE_FLAG_VERBOSE, 0)
File "/usr/lib/python3.6/sre_parse.py", line 416, in _parse_sub
not nested and not items))
File "/usr/lib/python3.6/sre_parse.py", line 502, in _parse
code = _escape(source, this, state)
File "/usr/lib/python3.6/sre_parse.py", line 401, in _escape
raise source.error("bad escape %s" % escape, len(escape))
sre_constants.error: bad escape \u at position 0
Complete stack trace for using '\x12\xe7' as replacement.
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/mitmproxy/tools/console/master.py", line 281, in run
self.loop.run()
File "/usr/lib/python3/dist-packages/urwid/main_loop.py", line 278, in run
self._run()
File "/usr/lib/python3/dist-packages/urwid/main_loop.py", line 376, in _run
self.event_loop.run()
File "/usr/lib/python3/dist-packages/urwid/main_loop.py", line 682, in run
self._loop()
File "/usr/lib/python3/dist-packages/urwid/main_loop.py", line 715, in _loop
alarm_callback()
File "/usr/lib/python3/dist-packages/urwid/main_loop.py", line 164, in cb
callback(self, user_data)
File "/usr/lib/python3/dist-packages/mitmproxy/tools/console/master.py", line 239, in ticker
changed = self.tick(timeout=0)
File "/usr/lib/python3/dist-packages/mitmproxy/master.py", line 109, in tick
handle_func(obj)
File "/usr/lib/python3/dist-packages/mitmproxy/controller.py", line 70, in wrapper
master.addons(f.name, message)
File "/usr/lib/python3/dist-packages/mitmproxy/addonmanager.py", line 90, in call
self.invoke(i, name, *args, **kwargs)
File "/usr/lib/python3/dist-packages/mitmproxy/addonmanager.py", line 85, in invoke
func(*args, **kwargs)
File "/usr/lib/python3/dist-packages/mitmproxy/addons/replace.py", line 93, in response
self.execute(flow)
File "/usr/lib/python3/dist-packages/mitmproxy/addons/replace.py", line 83, in execute
self.replace(f.response, rex, s)
File "/usr/lib/python3/dist-packages/mitmproxy/addons/replace.py", line 100, in replace
obj.replace(rex, s, flags=re.DOTALL)
File "/usr/lib/python3/dist-packages/mitmproxy/net/http/message.py", line 257, in replace
pattern = strutils.escaped_str_to_bytes(pattern)
File "/usr/lib/python3/dist-packages/mitmproxy/utils/strutils.py", line 99, in escaped_str_to_bytes
return codecs.escape_decode(data)[0]
UnicodeEncodeError: 'utf-8' codec can't encode character '\udce7' in position 8: surrogates not allowed

fixed by #3486


It should be 'Environment Variables' rather than 'Ports' in pod detail view

Rancher versions:
rancher/rancher:v2.0.0
rancher/rancher-agent:v2.0.0
Infrastructure Stack versions:
kubernetes:rancher/hyperkube:v1.10.1-rancher2
Steps to Reproduce:

[Workloads] Click on one workload to navigate to its detail view.
[Workload] Click on one pod to navigate to its pod view.

Results:
[Pod:XXX]There are two 'Ports' categories as shown in attached snapshot.

@NG85 - This has already been fixed in the latest release.  Please update to 2.0.2


⚠ Bofrost.es has degraded performance

In 46e9d0b, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1531 ms

Resolved: Bofrost.es performance has improved in 7598745 after 6 minutes.


Add color control to qpg lighting example

Problem
After the addition of color cluster implementation, control can be added to lighting example, to actually trigger the LED according to cluster commands.
Change overview
This PR adds the necessary implementation to lighting example so the changes done in color control cluster are transformed to RGB space and sent to LED for display.


Linting

Hi all,
Your group's progress is impressive. I think you're all set once you add the Linting Action for your tasks.

@Mosaddeq107 Thanks for your comment, however we haven't done Task 2 and Task 3 yet. What about you?

@Mosaddeq107 Thanks for your comment, however we haven't done Task 2 and Task 3 yet. What about you?

We are having an issue with no maintainer. Therefore, our works aren't visible to others.

@Mosaddeq107 Task 2 and 3 are still remaining, but yeah we will finish it soon. Why is there no maintainer? You can be the one.

Are you only 2 people in the group? @tirthbha

And also, I assume, all the people are working, but maybe they did not update their repository (main/merged) yet. I think its good if they do, so that we can peek into other's work too and know more.

We are 3, @uarif . I haven't started yet, because I am doing task three. I need to wait for the outcomes from task 1 and 2.

Yes, I understand, I was just talking generally. But good luck on your task, and yes, unless task1 and task2 are done you can not do yours.

I would suggest to start writing the introduction at least, You can write about your project and ffts, and then can add the other parts later.  @poojashresthacode

I would suggest to start writing the introduction at least, You can write about your project and ffts, and then can add the other parts later. @poojashresthacode

Good suggestion

Thank you


SCRUM-32: Removing not implemented

Fix:

So the CI can pass for the unimplemented project for branch protection

rev


Initial Redis cache support

Not yet ready to merge, but comments welcome.

Closing; superseded by MongoDB support (#95).


seg fault when running teapot example

when running cargo run --example teapot, i receive the following error:
    Finished dev [unoptimized + debuginfo] target(s) in 0.03s
     Running `target/debug/examples/teapot`
Segmentation fault (core dumped)

i tried to debug with gdb. i ran
gdb ./target/debug/examples/teapot-231767fafa056b68
within gdb i ran r
a window popped open and it looked like this:

and i received the following output:
Starting program: /home/marina/dev/rugl/target/debug/examples/teapot-231767fafa056b68
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7ffff08a8700 (LWP 59890)]
[New Thread 0x7fffebebe700 (LWP 59891)]
[New Thread 0x7fffeb6bd700 (LWP 59892)]
[New Thread 0x7fffeaebc700 (LWP 59893)]
[New Thread 0x7fffea6bb700 (LWP 59894)]
[New Thread 0x7fffe9eba700 (LWP 59895)]
[New Thread 0x7fffe96b9700 (LWP 59896)]
[New Thread 0x7fffe8eb8700 (LWP 59897)]
[New Thread 0x7fffcbfff700 (LWP 59898)]
[New Thread 0x7fffcb7fe700 (LWP 59899)]
[New Thread 0x7fffcaffd700 (LWP 59900)]
[New Thread 0x7fffca7fc700 (LWP 59901)]
[New Thread 0x7fffc9ffb700 (LWP 59902)]
[New Thread 0x7fffc97fa700 (LWP 59903)]
[New Thread 0x7fffc8ff9700 (LWP 59904)]
[New Thread 0x7fffabfff700 (LWP 59905)]

Thread 1 "teapot-231767fa" received signal SIGSEGV, Segmentation fault.
0x00007ffff65a1081 in ?? ()
   from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so

then, (still within gdb), i ran bt and received the following output:
#0  0x00007ffff65a1081 in ?? ()
   from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#1  0x00007ffff6544dfa in ?? ()
   from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#2  0x00007ffff65476a3 in ?? ()
   from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#3  0x00007ffff67e7f30 in ?? ()
   from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#4  0x00007ffff67e50af in ?? ()
   from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#5  0x00007ffff67e64f0 in ?? ()
   from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#6  0x00007ffff5d4d51d in ?? ()
   from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#7  0x00007ffff5d4130f in ?? ()
   from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#8  0x00007ffff7695d87 in glPrimitiveBoundingBox ()
   from /lib/x86_64-linux-gnu/libGLX_mesa.so.0
#9  0x00007ffff7688a15 in ?? ()
   from /lib/x86_64-linux-gnu/libGLX_mesa.so.0
#10 0x0000555555587122 in glutin::api::glx::ffi::glx::Glx::SwapBuffers (self=0x7fffffffd1a0, dpy=0x555555774a10, drawable=46137346)
    at /home/marina/dev/rugl/target/debug/build/glutin-2e3908c137668e95/out/glx_bindings.rs:558
#11 0x0000555555582602 in <glutin::api::glx::Context as glutin::GlContext>::swap_buffers (self=0x7fffffffd1a0)
    at /home/marina/.cargo/registry/src/mirrors.ustc.edu.cn-61ef6e0cd06fb9b8/glutin-0.8.1/src/api/glx/mod.rs:135
#12 0x0000555555582be5 in <glutin::platform::platform::x11::Window as glutin::GlContext>::swap_buffers (self=0x7fffffffd188)
    at /home/marina/.cargo/registry/src/mirrors.ustc.edu.cn-61ef6e0cd06fb9b8/glutin-0.8.1/src/platform/linux/x11.rs:286
#13 0x00005555555827e0 in <glutin::platform::platform::api_dispatch--Type <RET> for more, q to quit, c to continue without paging--btc<RET>
::Window as glutin::GlContext>::swap_buffers (self=0x7fffffffd180)
    at /home/marina/.cargo/registry/src/mirrors.ustc.edu.cn-61ef6e0cd06fb9b8/glutin-0.8.1/src/platform/linux/api_dispatch.rs:243
#14 0x0000555555582b6e in glutin::window::<impl glutin::Window>::swap_buffers (self=0x7fffffffd180)
    at /home/marina/.cargo/registry/src/mirrors.ustc.edu.cn-61ef6e0cd06fb9b8/glutin-0.8.1/src/window.rs:399
#15 0x000055555558227e in rugl::rugl::Rugl::frame (
    self=0x7fffffffd178, draw=...)
    at /home/marina/dev/rugl/src/rugl.rs:133
#16 0x000055555558352c in teapot::main () at examples/teapot.rs:74

Ah.. well dang. I'm not sure if you go back in time with your rust compiler version, it may be able to run. At this point this is an older experiment, and it's not running locally at all on my side anymore. I'm not really sure without digging into it further. Did you have an interest with this code? It's not really maintained and was an early learning of experiment of mine.

Nice! Yeah, this was part of my early learnings for Rust, but the compiler has changed as well as my own understanding of Rust, so this might be a bit outdated. I have some local work I never pushed up as well, although I don't really remember the state of it: https://github.com/gregtatum/rugl/tree/non-pushed-work
Your specific error looks like some issue with the glutin dependency. Perhaps the OS-level bindings have changed, and that dependency needs to be updated. I'm also not sure if this ever ran on Linux either, since I work on a Mac.


Enable rendering of Indian languages, by reading and utilizing the GSUB table

Implemented proper rendering of Indian languages, which need extensive Glyph substitution. The GSUB table has been read and used effectively to replace some compound words with their respective Glyphs. All tests are passing. I have tested this for the Bengali font. Please review these changes and let me know if it makes sense to incorporate these.
Thanks,
Palash.

Hello, yes, thanks, there has been a need for this for years... however this is a read only repository so you'll have to open an issue in JIRA ( https://issues.apache.org/jira/browse/PDFBOX ). We'll also need an ICLA, please read https://www.apache.org/licenses/icla.pdf , sign and submit it as explained in https://www.apache.org/licenses/#clas .
I only had a quick look (I just woke up), I noticed that there are a few tables and a font. Where do these come from? I see this is only for test so in the worst case we could download it. (Make a text search for "PDFBOX-4038" to see how this is done). We also need the apache header for any new non binary files.
If not in your proposed patch, it would be nice to have an example with a simple text that would not look OK without your patch.
Does your patch change any API ina "breaking" way? If yes it will be used for the trunk only, if not then it could also be used for 2.0.

The font license is OK, we'll only have to include the license text:
https://www.apache.org/legal/resolved.html#category-b

I entered "The quick brown fox jumps over the lazy dog" into Google translate, and the result was "দ্রুত গাঢ় শেয়াল অলস কুকুর জুড়ে জাম্প". Then I created a PDF file with this. With your font, I got a line with incomplete glyphs:
example-new.pdf
Code:
                PDFont font7 = PDType0Font.load(document, new File("Lohit-Bengali.ttf"));
                stream.setFont(font7, 12);
                stream.newLine();
                stream.showText("দ্রুত গাঢ় শেয়াল অলস কুকুর জুড়ে জাম্প");

Hi Tilman,
Thanks a lot for the quick response. Please find my reply below:

ICLA: Sure, I would send you a signed/scanned copy by 16th April, Monday
apache header for any new non binary files: Done
example with a simple text: Done: /pdfbox-examples/src/main/java/org/apache/pdfbox/examples/pdmodel/BengaliPdfGenerationHelloWorld.java.
Please find attached the before/after pdf files
Bengali-text-after.pdf
Bengali-text-before.pdf
Does your patch change any API in a "breaking" way: I don't think so, the only "major" change I did is made PDFont::encode(String text) non-final, and overrode it in PDType0Font
Incomplete Bengali text with my changes: Not sure, I just ran it, able to get "almost" complete file, using jdk8.
a.pdf

Thanks,
Palash.

Closing the pull request, as the files have been checked in to the trunk by Tilman Hausherr: https://svn.apache.org/r1829710


The dataflows feature (in preview) is not supported on Multi-GEO at this time.

Dataflows are GA since april 2nd, 2019.  What is the status with the multi-geo support of dataflows?
https://powerbi.microsoft.com/en-us/blog/announcing-power-bi-dataflows-general-availability/

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

ID: 2e1ae590-933f-bf65-888e-03dbf0ddc252
Version Independent ID: ae8f54bb-5fdb-a071-528d-169b4b766be6
Content: Multi-Geo support for Power BI Premium - Power BI
Content Source: powerbi-docs/service-admin-premium-multi-geo.md
Service: powerbi
Sub-service: powerbi-admin
GitHub Login: @mgblythe
Microsoft Alias: mblythe

Thanks for your comment, @snotebaert . We’ve forwarded your feedback to the writer, who should respond to this thread shortly. Thanks!

Thanks @snotebaert - I'll review the (preview). I don't see any reference to multi-geo support in the release plan.

Fix verified, closing.


About OLAF simulation time

Dear all and @ebranlard
I calculated the NREL5MW model, and calculated the time required for 10 times wake sites through py program. The time step was 0.08264, the total calculation revolution was 86rot, and the calculation time was 417s. My four wake plane numbers are defined as 2507(41.78rot), 208(3.47rot), 2445(40.75rot), and 0 respectively. But my calculation always stops automatically in about 80 or 90 seconds, may I ask why?
BR,
Roby

Hi,
I'm not sure what is happening. Here's a couple of questions to help figure it out:

If you run with BEM (WakeMod=1), do you have the same issue?
Which version of OpenFAST are you using, which platform and compiler ?
Can you monitor your memory and see if maybe you run out of memory right before the end of simulation? Is the memory continuously increasing?
Is there anything written on the terminal before the simulation stops?
Can you run without a farwake and just a near wake? Set nFW=0 nFWFree=0
If none of this give us insights, can you share all of your simulation input files?
Cheers,

Emmanuel

Hi ebranlard
I used the Aerodyn_Driver.exe obtained from the Aerodyn module compiled in version 3.4.1 to run the case.
I have tried many of the following:
NW
NW+NWFree
NW+NWFree+FW
NW+FW
The program stops at 93s no matter how you set it.
I tried running it on two different computers with 16GB of running memory, and closed other memory-hogging applications.
After the program runs without any error, the program stops after 93s, and then the hard disk character and cursor appear.
Here is a file of one of my cases.

Hi @robytian
Thank you for testing.

Does the case run with WakeMod=1?
Can you share your all of your simulation input files as a zip file?
Thanks

Hi @ebranlard
The case I used was the helix case, which doesn't seem to have WakeMod. No matter how I set this up, it's only going to run 93 seconds.
Here is my case.
1.zip
BR,
Roby

Hi Roby
When I ran your testcase with your executable I got the following error in the terminal at about 93s:
forrtl: severe (170): Program Exception - stack overflow
You can try increasing the stack size in your Visual Studio solution: Right click on the AeroDyn solution:
Properties -> Linker -> System -> Stack Reserve Size
and set it to a larger number, for instance 999999999. Let me know if that works.
A couple of other recommendations:

you can set VTK_fps to 1 or low value to limit the number of VTK outputs and disk space.
you can update to v3.5.0.

I hope that helps,
Emmanuel

Hi Emmanuel
I used the code compiled in version 3.4.1 to run for 300s, all set to free near wake panels, 10m/s, 10rpm, 0.1 step length, about 10 hours. Now I run 300s with version 3.5 code, set to 11.4m/s, 12.1rpm, 0.0826 steps, and have not finished running for more than 2 days. Can you guess what the reason is?
BR,
Roby

Hi Roby,
Does the application report that "OpenMP is enabled" and give a number of threads?
Are you using VelocityMethod=2?

Hi Emmanuel
Oh, my VelocityMethod chose 1, which may be the reason for the slow calculation. In addition, it is mentioned in the literature that the increase of wind speed leads to the increase of calculation time, which I think is reasonable. This is a 16-thread i7 processor, calculate 11.4m/s, free near wake panels 3630, this speed should be normal.

BR，
Roby

Hi Roby,
Yes, the slow computational time comes from the use of the N^2 method (VelocityMethod=1). The tree algorithm will drastically lower the computational time (at a small loss of accuracy cost).


Z-WAVE-SERVER: Cannot send this message because it would exceed the maximum payload length! (ZW0215)

Is your problem within Home Assistant (Core or Z-Wave JS Integration)?
YES, BUT a Home Assistant developer has told me to come here
Is your problem within Z-Wave JS UI (formerly ZwaveJS2MQTT)?
NO, my problem is NOT within Z-Wave JS UI
Checklist

[X] I have checked the troubleshooting section and my problem is not described there.

[X] I have read the changelog and my problem was not mentioned there.

Describe the bug
What causes the bug?
Call a scene to set a light to a color and brightness level, when the light is already on.
What do you observe?
Says error ZW0215.
What did you expect to happen?
The light to change color.
Steps to reproduce the behavior:
Set a scene in HA, call it = ok
Call another scene = nok error.
Turn off the light
turn it immediately back on
Call the scene = ok
Device information
Manufacturer: Qubino
Model name:  ZMNKAD1
Node ID in your network: 60
Device ID 345-82-8 (0x0159-0x0008-0x0052)
How are you using node-zwave-js?

[X] zwave-js-ui (formerly zwavejs2mqtt) Docker image (latest)
[ ] zwave-js-ui (formerly zwavejs2mqtt) Docker image (dev)
[ ] zwave-js-ui (formerly zwavejs2mqtt) Docker manually built (please specify branches)
[ ] ioBroker.zwave2 adapter (please specify version)
[ ] HomeAssistant zwave_js integration  (please specify version)
[ ] pkg
[ ] node-red-contrib-zwave-js (please specify version, double click node to find out)
[ ] Manually built from GitHub (please specify branch)
[ ] Other (please describe)

Which branches or versions?
zwave-js-ui: <IP_ADDRESS>a6f57
zwave-js: 10.14.0
home id:<PHONE_NUMBER>
home hex: 0xcd00c016
Did you change anything?
no
If yes, what did you change?
No response
Did this work before?
Yes (please describe)
If yes, where did it work?
50/50 of the times this works, so rather doesn't work unless turning off the light.
Attach Driver Logfile
18:37:03.275 SERIAL « 0x010e0004000b0631050422095dd4006a (16 bytes)
18:37:03.278 SERIAL » [ACK] (0x06)
18:37:03.281 CNTRLR [Node 011] [Multilevel Sensor] Power: metadata updated [Endpoint 0]
18:37:03.284 CNTRLR [Node 011] [~] [Multilevel Sensor] Power: 202.9 => 239.7 [Endpoint 0]
18:37:03.286 DRIVER « [Node 011] [REQ] [ApplicationCommand]
└─[MultilevelSensorCCReport]
type: Power
scale: Watt
value: 239.7
18:37:07.275 SERIAL « 0x010e0004000b063105042207c5d400fc (16 bytes)
18:37:07.278 SERIAL » [ACK] (0x06)
18:37:07.281 CNTRLR [Node 011] [Multilevel Sensor] Power: metadata updated [Endpoint 0]
18:37:07.284 CNTRLR [Node 011] [~] [Multilevel Sensor] Power: 239.7 => 198.9 [Endpoint 0]
18:37:07.286 DRIVER « [Node 011] [REQ] [ApplicationCommand]
└─[MultilevelSensorCCReport]
type: Power
scale: Watt
value: 198.9
18:37:12.275 SERIAL « 0x010e0004000b063105042209abd4009c (16 bytes)
18:37:12.280 SERIAL » [ACK] (0x06)
18:37:12.289 CNTRLR [Node 011] [Multilevel Sensor] Power: metadata updated [Endpoint 0]
18:37:12.294 CNTRLR [Node 011] [~] [Multilevel Sensor] Power: 198.9 => 247.5 [Endpoint 0]
18:37:12.298 DRIVER « [Node 011] [REQ] [ApplicationCommand]
└─[MultilevelSensorCCReport]
type: Power
scale: Watt
value: 247.5
18:37:17.275 SERIAL « 0x010e0004000b06310504220827d40011 (16 bytes)
18:37:17.277 SERIAL » [ACK] (0x06)
18:37:17.280 CNTRLR [Node 011] [Multilevel Sensor] Power: metadata updated [Endpoint 0]
18:37:17.284 CNTRLR [Node 011] [~] [Multilevel Sensor] Power: 247.5 => 208.7 [Endpoint 0]
18:37:17.286 DRIVER « [Node 011] [REQ] [ApplicationCommand]
└─[MultilevelSensorCCReport]
type: Power
scale: Watt
value: 208.7
18:37:22.311 SERIAL » 0x010a00133c039f01c62513b7 (12 bytes)
18:37:22.313 DRIVER » [Node 060] [REQ] [SendData]
│ transmit options: 0x25
│ callback id: 19
└─[Security2CCNonceGet]
sequence number: 198
18:37:22.317 SERIAL « [ACK] (0x06)
18:37:22.320 SERIAL « 0x0104011301e8 (6 bytes)
18:37:22.322 SERIAL » [ACK] (0x06)
18:37:22.324 DRIVER « [RES] [SendData]
was sent: true
18:37:22.381 SERIAL « 0x011800131300000701cd7f7f7f7f0101030c0000000201000020 (26 bytes)
18:37:22.383 SERIAL » [ACK] (0x06)
18:37:22.385 DRIVER « [REQ] [SendData]
callback id: 19
transmit status: OK, took 70 ms
repeater node IDs: 12
routing attempts: 1
protocol & route speed: Z-Wave, 40 kbit/s
ACK RSSI: -51 dBm
ACK RSSI on repeaters: N/A
ACK channel no.: 1
TX channel no.: 1
18:37:22.463 SERIAL « 0x011c0004003c149f020001338e4445f5e9ade3757693e7a4297a0dcd00fd (30 bytes)
18:37:22.465 SERIAL » [ACK] (0x06)
18:37:22.467 DRIVER « [Node 060] [REQ] [ApplicationCommand]
└─[Security2CCNonceReport]
sequence number: 0
SOS: true
MOS: false
receiver entropy: 0x338e4445f5e9ade3757693e7a4297a0d
2023-04-13 18:37:22.483 ERROR Z-WAVE-SERVER: Cannot send this message because it would exceed the maximum payload length! (ZW0215)
ZWaveError: Cannot send this message because it would exceed the maximum payload length! (ZW0215)
at Driver.sendMessage (/usr/src/app/node_modules/zwave-js/src/lib/driver/Driver.ts:4182:23)
at Driver.sendCommandInternal (/usr/src/app/node_modules/zwave-js/src/lib/driver/Driver.ts:4375:28)
at Driver.sendSupervisedCommand (/usr/src/app/node_modules/zwave-js/src/lib/driver/Driver.ts:4420:27)
at Driver.sendCommand (/usr/src/app/node_modules/zwave-js/src/lib/driver/Driver.ts:4477:30)
at ColorSwitchCCAPI.set (/usr/src/app/node_modules/@zwave-js/cc/src/cc/ColorSwitchCC.ts:232:38)
at Proxy.ColorSwitchCCAPI.<computed> (/usr/src/app/node_modules/@zwave-js/cc/src/cc/ColorSwitchCC.ts:461:17)
at ZWaveNode.setValue (/usr/src/app/node_modules/zwave-js/src/lib/node/Node.ts:961:29)
at NodeMessageHandler.handle (/usr/src/app/node_modules/@zwave-js/server/dist/lib/node/message_handler.js:23:38)
at Object.node (/usr/src/app/node_modules/@zwave-js/server/dist/lib/server.js:41:96)
at Client.receiveMessage (/usr/src/app/node_modules/@zwave-js/server/dist/lib/server.js:106:99)
18:37:28.866 SERIAL » 0x0103003bc7 (5 bytes)
18:37:28.869 DRIVER » [REQ] [GetBackgroundRSSI]
18:37:28.874 SERIAL « [ACK] (0x06)
18:37:28.878 SERIAL « 0x0105013bb5aedb (7 bytes)
18:37:28.885 SERIAL » [ACK] (0x06)
18:37:28.889 DRIVER « [RES] [GetBackgroundRSSI]
channel 0: -75 dBm
channel 1: -82 dBm
18:37:36.508 SERIAL » 0x012500133c1e9f03c800e3ba6453bc2ccfa2dcdca85024239f377a0d8bb94deb2 (39 bytes)
e651cd025142e
18:37:36.514 DRIVER » [Node 060] [REQ] [SendData]
│ transmit options: 0x25
│ callback id: 20
└─[Security2CCMessageEncapsulation]
│ sequence number: 200
└─[MultiChannelCCCommandEncapsulation]
│ source: 0
│ destination: 1
└─[SupervisionCCGet]
│ session id: 59
│ request updates: true
└─[ColorSwitchCCSet]
Red: 255
Green: 255
Blue: 0
duration: default
18:37:36.518 SERIAL « [ACK] (0x06)
18:37:36.522 SERIAL « 0x0104011301e8 (6 bytes)
18:37:36.528 SERIAL » [ACK] (0x06)
18:37:36.531 DRIVER « [RES] [SendData]
was sent: true
18:37:36.594 SERIAL « 0x011800131400000801c97f7f7f7f0101030c000000020100002c (26 bytes)
18:37:36.596 SERIAL » [ACK] (0x06)
18:37:36.600 DRIVER « [REQ] [SendData]
callback id: 20
transmit status: OK, took 80 ms
repeater node IDs: 12
routing attempts: 1
protocol & route speed: Z-Wave, 40 kbit/s
ACK RSSI: -55 dBm
ACK RSSI on repeaters: N/A
ACK channel no.: 1
TX channel no.: 1
18:37:36.684 SERIAL « 0x011c0004003c149f020101d4ab991d0eeceb432f64d8feaa825176cd004c (30 bytes)
18:37:36.686 SERIAL » [ACK] (0x06)
18:37:36.690 DRIVER « [Node 060] [REQ] [ApplicationCommand]
└─[Security2CCNonceReport]
sequence number: 1
SOS: true
MOS: false
receiver entropy: 0xd4ab991d0eeceb432f64d8feaa825176
18:37:36.699 CNTRLR [Node 060] failed to decode the message, retrying with SPAN extension...
2023-04-13 18:37:36.713 ERROR Z-WAVE-SERVER: Cannot send this message because it would exceed the maximum payload length! (ZW0215)
ZWaveError: Cannot send this message because it would exceed the maximum payload length! (ZW0215)
at Driver.sendMessage (/usr/src/app/node_modules/zwave-js/src/lib/driver/Driver.ts:4182:23)
at Driver.sendCommandInternal (/usr/src/app/node_modules/zwave-js/src/lib/driver/Driver.ts:4375:28)
at Driver.sendSupervisedCommand (/usr/src/app/node_modules/zwave-js/src/lib/driver/Driver.ts:4420:27)
at Driver.sendCommand (/usr/src/app/node_modules/zwave-js/src/lib/driver/Driver.ts:4477:30)
at ColorSwitchCCAPI.set (/usr/src/app/node_modules/@zwave-js/cc/src/cc/ColorSwitchCC.ts:232:38)
at Proxy.ColorSwitchCCAPI.<computed> (/usr/src/app/node_modules/@zwave-js/cc/src/cc/ColorSwitchCC.ts:461:17)
at ZWaveNode.setValue (/usr/src/app/node_modules/zwave-js/src/lib/node/Node.ts:961:29)
at NodeMessageHandler.handle (/usr/src/app/node_modules/@zwave-js/server/dist/lib/node/message_handler.js:23:38)
at Object.node (/usr/src/app/node_modules/@zwave-js/server/dist/lib/server.js:41:96)
at Client.receiveMessage (/usr/src/app/node_modules/@zwave-js/server/dist/lib/server.js:106:99)
18:37:58.378 SERIAL » 0x012500133c1e9f03ca0012a048d49e862832cd38d9b48b4dbe47c7a4292d8036f (39 bytes)
510c3582515a9
18:37:58.384 DRIVER » [Node 060] [REQ] [SendData]
│ transmit options: 0x25
│ callback id: 21
└─[Security2CCMessageEncapsulation]
│ sequence number: 202
└─[MultiChannelCCCommandEncapsulation]
│ source: 0
│ destination: 1
└─[SupervisionCCGet]
│ session id: 60
│ request updates: true
└─[ColorSwitchCCSet]
Red: 255
Green: 255
Blue: 0
duration: default
18:37:58.391 SERIAL « [ACK] (0x06)
18:37:58.398 SERIAL « 0x0104011301e8 (6 bytes)
18:37:58.402 SERIAL » [ACK] (0x06)
18:37:58.406 DRIVER « [RES] [SendData]
was sent: true
18:37:58.466 SERIAL « 0x011800131500000701cd7f7f7f7f0101030c0000000201000026 (26 bytes)
18:37:58.470 SERIAL » [ACK] (0x06)
18:37:58.474 DRIVER « [REQ] [SendData]
callback id: 21
transmit status: OK, took 70 ms
repeater node IDs: 12
routing attempts: 1
protocol & route speed: Z-Wave, 40 kbit/s
ACK RSSI: -51 dBm
ACK RSSI on repeaters: N/A
ACK channel no.: 1
TX channel no.: 1
18:37:58.553 SERIAL « 0x011c0004003c149f0202016cbffbaca33b43be4ea7a862075e512bcd007d (30 bytes)
18:37:58.556 SERIAL » [ACK] (0x06)
18:37:58.559 DRIVER « [Node 060] [REQ] [ApplicationCommand]
└─[Security2CCNonceReport]
sequence number: 2
SOS: true
MOS: false
receiver entropy: 0x6cbffbaca33b43be4ea7a862075e512b
18:37:58.564 CNTRLR [Node 060] failed to decode the message, retrying with SPAN extension...
2023-04-13 18:37:58.576 ERROR Z-WAVE-SERVER: Cannot send this message because it would exceed the maximum payload length! (ZW0215)
ZWaveError: Cannot send this message because it would exceed the maximum payload length! (ZW0215)
at Driver.sendMessage (/usr/src/app/node_modules/zwave-js/src/lib/driver/Driver.ts:4182:23)
at Driver.sendCommandInternal (/usr/src/app/node_modules/zwave-js/src/lib/driver/Driver.ts:4375:28)
at Driver.sendSupervisedCommand (/usr/src/app/node_modules/zwave-js/src/lib/driver/Driver.ts:4420:27)
at Driver.sendCommand (/usr/src/app/node_modules/zwave-js/src/lib/driver/Driver.ts:4477:30)
at ColorSwitchCCAPI.set (/usr/src/app/node_modules/@zwave-js/cc/src/cc/ColorSwitchCC.ts:232:38)
at Proxy.ColorSwitchCCAPI.<computed> (/usr/src/app/node_modules/@zwave-js/cc/src/cc/ColorSwitchCC.ts:461:17)
at ZWaveNode.setValue (/usr/src/app/node_modules/zwave-js/src/lib/node/Node.ts:961:29)
at NodeMessageHandler.handle (/usr/src/app/node_modules/@zwave-js/server/dist/lib/node/message_handler.js:23:38)
at Object.node (/usr/src/app/node_modules/@zwave-js/server/dist/lib/server.js:41:96)
at Client.receiveMessage (/usr/src/app/node_modules/@zwave-js/server/dist/lib/server.js:106:99)
18:38:03.586 SERIAL » 0x0103003bc7 (5 bytes)
18:38:03.588 DRIVER » [REQ] [GetBackgroundRSSI]
18:38:03.591 SERIAL « [ACK] (0x06)
18:38:03.594 SERIAL « 0x0105013bb3abd8 (7 bytes)
18:38:03.596 SERIAL » [ACK] (0x06)
18:38:03.599 DRIVER « [RES] [GetBackgroundRSSI]
channel 0: -77 dBm
channel 1: -85 dBm
18:38:21.694 SERIAL » 0x011f00133c189f03cc00826e50950dbadf9a3232070565ed925a74630e862516b (33 bytes)
2
18:38:21.697 DRIVER » [Node 060] [REQ] [SendData]
│ transmit options: 0x25
│ callback id: 22
└─[Security2CCMessageEncapsulation]
│ sequence number: 204
└─[MultiChannelCCCommandEncapsulation]
│ source: 0
│ destination: 1
└─[SupervisionCCGet]
│ session id: 61
│ request updates: true
└─[MultilevelSwitchCCSet]
target value: 255
duration: default
18:38:21.701 SERIAL « [ACK] (0x06)
18:38:21.706 SERIAL « 0x0104011301e8 (6 bytes)
18:38:21.708 SERIAL » [ACK] (0x06)
18:38:21.714 DRIVER « [RES] [SendData]
was sent: true
18:38:21.776 SERIAL « 0x011800131600000701ca7f7f7f7f0101030c0000000201000022 (26 bytes)
18:38:21.777 SERIAL » [ACK] (0x06)
18:38:21.779 DRIVER « [REQ] [SendData]
callback id: 22
transmit status: OK, took 70 ms
repeater node IDs: 12
routing attempts: 1
protocol & route speed: Z-Wave, 40 kbit/s
ACK RSSI: -54 dBm
ACK RSSI on repeaters: N/A
ACK channel no.: 1
TX channel no.: 1
18:38:21.863 SERIAL « 0x011c0004003c149f0203014ae04d3de2b1b9687a5aeb3c4c28ae42cd00ba (30 bytes)
18:38:21.865 SERIAL » [ACK] (0x06)
18:38:21.867 DRIVER « [Node 060] [REQ] [ApplicationCommand]
└─[Security2CCNonceReport]
sequence number: 3
SOS: true
MOS: false
receiver entropy: 0x4ae04d3de2b1b9687a5aeb3c4c28ae42
18:38:21.872 CNTRLR [Node 060] failed to decode the message, retrying with SPAN extension...
18:38:21.886 SERIAL » 0x013100133c2a9f03cd01124142398828dad6240034497807c79aa973aa9e72e9c (51 bytes)
620d1db8d22fef67497982aed89f7732517d9
18:38:21.888 DRIVER » [Node 060] [REQ] [SendData]
│ transmit options: 0x25
│ callback id: 23
└─[Security2CCMessageEncapsulation]
│ sequence number: 205
│ extensions:
│ · type: SPAN
│ sender EI: 0x42398828dad6240034497807c79aa973
└─[MultiChannelCCCommandEncapsulation]
│ source: 0
│ destination: 1
└─[SupervisionCCGet]
│ session id: 61
│ request updates: true
└─[MultilevelSwitchCCSet]
target value: 255
duration: default
18:38:21.892 SERIAL « [ACK] (0x06)
18:38:21.899 SERIAL « 0x0104011301e8 (6 bytes)
18:38:21.901 SERIAL » [ACK] (0x06)
18:38:21.903 DRIVER « [RES] [SendData]
was sent: true
18:38:22.037 SERIAL « 0x011800131700000e01cd7f7f7f7f0101030c000000020100002d (26 bytes)
18:38:22.039 SERIAL » [ACK] (0x06)
18:38:22.044 DRIVER « [REQ] [SendData]
callback id: 23
transmit status: OK, took 140 ms
repeater node IDs: 12
routing attempts: 1
protocol & route speed: Z-Wave, 40 kbit/s
ACK RSSI: -51 dBm
ACK RSSI on repeaters: N/A
ACK channel no.: 1
TX channel no.: 1
18:38:22.124 SERIAL « 0x011d0004003c159f03040087a09b8db2ab822c956ebd747cf99f49e4cd0099 (31 bytes)
18:38:22.128 SERIAL » [ACK] (0x06)
18:38:22.130 DRIVER « [Node 060] [REQ] [ApplicationCommand]
└─[Security2CCMessageEncapsulation]
│ sequence number: 4
└─[MultiChannelCCCommandEncapsulation]
│ source: 1
│ destination: 0
└─[SupervisionCCReport]
session id: 61
more updates follow: false
status: Success
duration: 0s
18:38:27.170 SERIAL » 0x011900133c129f03ce007b5b9d84cfed6b8765ced2cf65f1251861 (27 bytes)
18:38:27.173 DRIVER » [Node 060] [REQ] [SendData]
│ transmit options: 0x25
│ callback id: 24
└─[Security2CCMessageEncapsulation]
│ sequence number: 206
└─[MultiChannelCCCommandEncapsulation]
│ source: 0
│ destination: 1
└─[MultilevelSwitchCCGet]
18:38:27.179 SERIAL « [ACK] (0x06)
18:38:27.185 SERIAL « 0x0104011301e8 (6 bytes)
18:38:27.188 SERIAL » [ACK] (0x06)
18:38:27.192 DRIVER « [RES] [SendData]
was sent: true
18:38:27.259 SERIAL « 0x011800131800000801cd7f7f7f7f0101030c0000000201000024 (26 bytes)
18:38:27.261 SERIAL » [ACK] (0x06)
18:38:27.263 DRIVER « [REQ] [SendData]
callback id: 24
transmit status: OK, took 80 ms
repeater node IDs: 12
routing attempts: 1
protocol & route speed: Z-Wave, 40 kbit/s
ACK RSSI: -51 dBm
ACK RSSI on repeaters: N/A
ACK channel no.: 1
TX channel no.: 1
18:38:27.344 SERIAL « 0x011d0004003c159f030500e83003635d56a639afab92f72f0a446f97cd004f (31 bytes)
18:38:27.348 SERIAL » [ACK] (0x06)
18:38:27.351 CNTRLR [Node 060] [~] [Multilevel Switch] targetValue: 255 => 99 [Endpoint 1]
18:38:27.354 CNTRLR [Node 060] [~] [Multilevel Switch] duration: {"value":0,"unit":"s [Endpoint 1]
econds"} => {"value":0,"unit":"seconds"}
18:38:27.356 CNTRLR [Node 060] [~] [Multilevel Switch] currentValue: 0 => 99 [Endpoint 1]
18:38:27.359 DRIVER « [Node 060] [REQ] [ApplicationCommand]
└─[Security2CCMessageEncapsulation]
│ sequence number: 5
└─[MultiChannelCCCommandEncapsulation]
│ source: 1
│ destination: 0
└─[MultilevelSwitchCCReport]
current value: 99
target value: 99
duration: 0s
18:38:28.321 SERIAL « 0x010e0004000d06310504220026d0001a (16 bytes)
18:38:28.324 SERIAL » [ACK] (0x06)
18:38:28.327 CNTRLR [Node 013] [Multilevel Sensor] Power: metadata updated [Endpoint 0]
18:38:28.330 CNTRLR [Node 013] [~] [Multilevel Sensor] Power: 3.9 => 3.8 [Endpoint 0]
18:38:28.332 DRIVER « [Node 013] [REQ] [ApplicationCommand]
└─[MultilevelSensorCCReport]
type: Power
scale: Watt
value: 3.8
18:38:33.595 SERIAL » 0x0103003bc7 (5 bytes)
18:38:33.598 DRIVER » [REQ] [GetBackgroundRSSI]
18:38:33.604 SERIAL « [ACK] (0x06)
18:38:33.609 SERIAL « 0x0105013bb1b1c0 (7 bytes)
18:38:33.613 SERIAL » [ACK] (0x06)
18:38:33.618 DRIVER « [RES] [GetBackgroundRSSI]
channel 0: -79 dBm
channel 1: -79 dBm
18:38:33.700 SERIAL » 0x012500133c1e9f03cf009f34fc83649cab4d75166cb2797b3865a7c0dcc90c5b7 (39 bytes)
82c1a95251952
18:38:33.704 DRIVER » [Node 060] [REQ] [SendData]
│ transmit options: 0x25
│ callback id: 25
└─[Security2CCMessageEncapsulation]
│ sequence number: 207
└─[MultiChannelCCCommandEncapsulation]
│ source: 0
│ destination: 1
└─[SupervisionCCGet]
[debuglog.txt](https://github.com/zwave-js/node-zwave-js/files/11225541/debuglog.txt)

│ session id: 62
│ request updates: true
└─[ColorSwitchCCSet]
Red: 255
Green: 0
Blue: 0
duration: default
18:38:33.709 SERIAL « [ACK] (0x06)
18:38:33.714 SERIAL « 0x0104011301e8 (6 bytes)
18:38:33.716 SERIAL » [ACK] (0x06)
18:38:33.719 DRIVER « [RES] [SendData]
was sent: true
18:38:33.796 SERIAL « 0x011800131900000801cd7f7f7f7f0101030c0000000201000025 (26 bytes)
18:38:33.798 SERIAL » [ACK] (0x06)
18:38:33.801 DRIVER « [REQ] [SendData]
callback id: 25
transmit status: OK, took 80 ms
repeater node IDs: 12
routing attempts: 1
protocol & route speed: Z-Wave, 40 kbit/s
ACK RSSI: -51 dBm
ACK RSSI on repeaters: N/A
ACK channel no.: 1
TX channel no.: 1
18:38:33.884 SERIAL « 0x011d0004003c159f03060046e7b2053eecfbf91fe914c57442c65821cd00f0 (31 bytes)
18:38:33.888 SERIAL » [ACK] (0x06)
18:38:33.892 DRIVER « [Node 060] [REQ] [ApplicationCommand]
└─[Security2CCMessageEncapsulation]
│ sequence number: 6
└─[MultiChannelCCCommandEncapsulation]
│ source: 1
│ destination: 0
└─[SupervisionCCReport]
session id: 62
more updates follow: false
status: Success
duration: 0s
18:38:33.901 CNTRLR [Node 060] [~] [Color Switch] currentColor[2]: 255 => 255 [Endpoint 1]
18:38:33.903 CNTRLR [Node 060] [~] [Color Switch] currentColor[3]: 0 => 0 [Endpoint 1]
18:38:33.906 CNTRLR [Node 060] [~] [Color Switch] currentColor[4]: 0 => 0 [Endpoint 1]
18:38:33.908 CNTRLR [Node 060] [~] [Color Switch] currentColor: {"red":255,"green":0, [Endpoint 1]
"blue":0} => {"red":255,"green":0,"blue":0}
18:38:33.911 CNTRLR [Node 060] [~] [Color Switch] targetColor: {"red":255,"green":0," [Endpoint 1]
blue":0} => {"red":255,"green":0,"blue":0}
18:38:33.916 CNTRLR [Node 060] [~] [Color Switch] hexColor: "ff0000" => "ff0000" [Endpoint 1]
18:38:33.939 SERIAL » 0x011f00133c189f03d000ff0ebaa68b75ad2eb808c0263ad0a6a1aac31014251ae (33 bytes)
2
18:38:33.945 DRIVER » [Node 060] [REQ] [SendData]
│ transmit options: 0x25
│ callback id: 26
└─[Security2CCMessageEncapsulation]
│ sequence number: 208
└─[MultiChannelCCCommandEncapsulation]
│ source: 0
│ destination: 1
└─[SupervisionCCGet]
│ session id: 63
│ request updates: true
└─[MultilevelSwitchCCSet]
target value: 25
duration: default
18:38:33.949 SERIAL « [ACK] (0x06)
18:38:33.954 SERIAL « 0x0104011301e8 (6 bytes)
18:38:33.956 SERIAL » [ACK] (0x06)
18:38:33.958 DRIVER « [RES] [SendData]
was sent: true
18:38:34.049 SERIAL « 0x011800131a00000901cd7f7f7f7f0101030c0000000201000027 (26 bytes)
18:38:34.050 SERIAL » [ACK] (0x06)
18:38:34.053 DRIVER « [REQ] [SendData]
callback id: 26
transmit status: OK, took 90 ms
repeater node IDs: 12
routing attempts: 1
protocol & route speed: Z-Wave, 40 kbit/s
ACK RSSI: -51 dBm
ACK RSSI on repeaters: N/A
ACK channel no.: 1
TX channel no.: 1
18:38:34.134 SERIAL « 0x011d0004003c159f030700019ebe62ce1eb9769c72e323ccdba05e19cd001b (31 bytes)
18:38:34.139 SERIAL » [ACK] (0x06)
18:38:34.141 DRIVER « [Node 060] [REQ] [ApplicationCommand]
└─[Security2CCMessageEncapsulation]
│ sequence number: 7
└─[MultiChannelCCCommandEncapsulation]
│ source: 1
│ destination: 0
└─[SupervisionCCReport]
session id: 63
more updates follow: false
status: Success
duration: 0s
18:38:34.148 CNTRLR [Node 060] [~] [Multilevel Switch] currentValue: 99 => 25 [Endpoint 1]

Can you tell me exactly what the scene is trying to set for which entity? I might also need a diagnostic dump for that device.

This is the yaml of the scenes I'm trying to call.

id: '1656341612753'
name: Badkamer Knop ROOD
entities:
light.badkamer_lichten:
supported_color_modes:
- hs
friendly_name: Badkamer LED lampje
supported_features: 32
color_mode: hs
brightness: 64
hs_color:
- 0
- 100
rgb_color:
- 255
- 0
- 0
xy_color:
- 0.701
- 0.299
state: 'on'
icon: mdi:bathtub
metadata:
light.badkamer_lichten:
entity_only: true
id: '1656341659630'
name: Badkamer LED geel
entities:
light.badkamer_lichten:
supported_color_modes:
- hs
friendly_name: Badkamer LED lampje
supported_features: 32
color_mode: hs
brightness: 255
hs_color:
- 60
- 100
rgb_color:
- 255
- 255
- 0
xy_color:
- 0.444
- 0.517
state: 'on'
icon: mdi:bathtub
metadata:
light.badkamer_lichten:
entity_only: true

Is there any way to set the brightness before the color?

Is there any way to set the brightness before the color?

Not in a scene. It's all in one.

I thought you maybe have an influence on the ordering of commands. It looks like it first sends the color change (the larger command), but that requires a re-sync of the encryption state, which puts it above the threshold. Then it sends the brightness change which is small enough to go through.

What was the automation that you tried to use? Did you try splitting up the brightness and color settings into separate actions? E.g. turn_on with brightness only, turn_on with color only.

I did, but even that did not always work.

Ok, looks like the command that should be transmitted is 48 bytes long. With explorer frames, the maximum is 46, without (but with routing) 48.
So we should be able to detect this and disable explorer frames when the payload is too long. Any longer won't work though, as routing would have to be disabled next.

@thecobra666 Can you please send me a re-interview log of that device?
It should support transport service, so I'm a bit confused why that's not being used here to get around the issue.

@thecobra666 Can you please send me a re-interview log of that device? It should support transport service, so I'm a bit confused why that's not being used here to get around the issue.
zwavejs_2023-04-14.log

As requested

Ok now I'm confused. It does support Transport Service CC v2, so the error you're seeing shouldn't be possible.
Just for my sanity, can you try activating the scene again now and log that?

Ok now I'm confused. It does support Transport Service CC v2, so the error you're seeing shouldn't be possible. Just for my sanity, can you try activating the scene again now and log that?

log.txt
That works just fine now and it's indeed using the transport service. I did had to reïnterview it again cause in HA it didn't identify as being able to change colors, yet in zwavejs-ui I did had the option to change it.

Ok that looks better. You probably had some communication troubles during the initial interview. Will close this then - the PR should make this better in case transport service is actually not supported.

Ok that looks better. You probably had some communication troubles during the initial interview. Will close this then - the PR should make this better in case transport service is actually not supported.

Is there a way for the end user to see when the interview was not finished correctly?

Not currently, but I plan to expose interview failures in a more fine-grained way:
https://github.com/zwave-js/node-zwave-js/issues/985


Added main menu tab “ElapsedTime”, and made it the entrance of the report on Roslyn Dashboard.

Copied from TFS work item #234585:
•       Added main menu tab “ElapsedTime”, and made it the entrance of the report.

Completed.