Ophir LOJKINE
Ophir LOJKINE
Connecting to the opcua server from inductive automation's ignition generates the following warning messages:  Does the server guarantee that it will send sequence numbers in order ?
Looking at the code base, it looks like all the datastructures are full of `Arc`. Notably, the address space is a ``Arc``. Would you be open to a big pull...
It looks like opcua-server has many duplicate dependencies ``` ❯ cargo tree --duplicates bytes v0.4.12 └── opcua-crypto v0.10.0 (/home/olojkine/dev/opcua-rust/crypto) ├── opcua-core v0.10.0 (/home/olojkine/dev/opcua-rust/core) │ └── opcua-server v0.10.0 (/home/olojkine/dev/opcua-rust/server) └── opcua-server...
This is related to but different from #166 : The opcua-server api expects the user to wrap their getters and setters in an `std::sync::Mutex` (https://docs.rs/opcua-server/0.8.1/opcua_server/address_space/variable/struct.Variable.html#method.set_value_setter), which means that two clients...
Hello, I cannot find in the documentation whether value getters and setters are supposed to be non-blocking or not. Looking at the code, it looks like they are indeed supposed...
Running `npm install isomorphic-webcrypto` downloads 200Mb of node modules, including all of react and react native. Maybe react native could be switched to a peerDependency ? ``` ❯ npm install...
The documentation contains the following example : ```ts sapper.start({ target: document.querySelector('#sapper') }); ``` However, `document.querySelector('#sapper')` can return `null`, but `sapper.start` does not accept null. It would be great to either...
In elm, `type` is a reserved keyword that can't be used as a function name, which results in a syntax that can be surprising and unintuitive when trying to use...
The following rust code: ```rust let file = OpenOptions::new().write(true).create(true).open("/tmp/myimage.png").unwrap(); let encoder = png::Encoder::new(file, 2, 2); encoder.write_header().unwrap().into_stream_writer_with_size(2); ``` never exits and creates the following never-ending file : ``` 00000000 89 50...
Hello ! This is not an issue, but a follow-up on: https://github.com/image-rs/image/issues/982#issuecomment-508858512 I finished implementing what I wanted to, and my results are quite disappointing, but I wanted to keep...