Thomas Bracht Laumann Jespersen
Thomas Bracht Laumann Jespersen
@damienpontifex Only the last two commits 05226a6 and f9d3f5d should be reviewed here. - 05226a6 is cherry-picked from PR #61 (commit d23b2699ccbd29e72e6a13a15a7270ee1d5b3d9c)
@ChristopherMacGown Thanks for the tip! I had to add version as well to `Cargo.lock`, like so: ``` [root] name="your-package-name" version="package-version" ``` worked like a charm.
Let me know if any additional information is required. At the moment, I think the probable culprit is the chroot - I can maybe someone else to try it out...
> > known failure on Windows, but not on Linux: > > That sounds very shady. Right?
Just an update. @flatcap confirmed the issue, and is working on revamping the colour management, which appears to fix it.
I forgot to mention that I also tried setting it to zero, but that also made the server abort the connection.
And just to clarify: I completely understand if this is a kind of "not our problem" issue :-) There will always be bad server implementations, I just wanted to raise...
> there's a [patch here](https://github.com/re-gmbh/opcua/commit/1986f0cd1e7705ec8ad554b42900233de2fa902c) - I'll try to find some time to create a MR for it. That's basically verbatim the [same patch](https://github.com/omnioiot/opcua/commit/b68a5a04f841e47769e80cd6480b86e3968ddbca) I ended up writing :-) Only...
Could this be related to #184?
@schroeder- > Len is a promis. Oof, that's not what I wanted to hear :-) but thanks! > DiagnosticsInfo are strange beast, do you realy want DiagnosticsInfo? Not necessarily, we...