rust
rust copied to clipboard
Rust implementation of the Varlink protocol
Updates the requirements on [colored_json](https://github.com/ctron/colored_json) to permit the latest version. Commits See full diff in compare view Dependabot will resolve any conflicts with this PR as long as you don't...
Updates the requirements on [peg](https://github.com/kevinmehall/rust-peg) to permit the latest version. Release notes Sourced from peg's releases. 0.8.1 Fixes Fix type inference for generic argument in rule's return position (#317) Fix...
I've got a quick question about the varlink generated error types. Take this generated code for example: ```rust pub enum ErrorKind { Varlink_Error, VarlinkReply_Error, Error(Option), HookFailed(Option), } ``` I have...
AFAICS the generator will always define a native Rust struct and offload the derivation of ``Deserialize`` and ``Serialize`` to Serde. Often it would be convenient if custom serialization could be...
I'm working on a project that uses varlink (c.f. https://github.com/nyarly/lorri/blob/stream_events/src/daemon/rpc.rs) It appears that clients connecting to the Monitor interface are leaking worker threads - even after those clients disconnect, the...
Using this with Podman will result in `invalid type: null, expected a sequence` on many endpoints, as empty lists are omitted in favor of `null`. I'm not sure if this...
Is there a recommended way to shutdown the Varlink server when it is started with `varlink::listen()`? I'm sure I could find a way to do it if I implemented the...
Instead of .take() for read and write stream, maybe just consume the connection and return it after success and disallow clone() for the connection
Perhaps I'm missing something but there doesn't seem to be a way to pass FDs? :thinking:
Since it's an IPC API, it should be async. Moreover, I think async should be the primary/main API, with blocking wrappers on top. I understand this is going to be...