Moritz Borcherding
Moritz Borcherding
This is useful for graceful shutdown of a service. When e.g. SIGTERM is sent to your service just stopping the process is pretty rough. dbus-daemon seems to handle it well...
Currently you would have to write that boilerplate code on your own. A proc-macro that derives the relevant getters and setters would be nice. Something like this trait should be...
Currently there are two ways processes for services are started. 1. Normal std::process::Command for helpers 2. Custom stuff for the main executable I am certain that even with the Command...
This is a list of control commands that I think should be supported in the future. Some of these are straight forward, and only miss code in the control interface...
Rsdctl just pretty prints the returned json from rustysd. To make this an actually useful tool it needs to be better in presenting the retrieved info/results/errors.
Logging
Rustysd needs persistent logging. This needs some questions answered: 1. Should rustysds logs go somewhere else than stdout/stderr output of services? 2. Should each service have it's own log or...
Rustysd needs a control interface command that triggers a complete reload of all units, which integrates changed / new units into the running system. Adding and activating new units should...
I need a place to put down some ideas for further optimizing this crate: ## Decoder 1. [ ] We only need to call reserve once for each block of...
I need some place to keep track of the tests I want to write before I feel comfortable doing a new release 1. [x] Tests for drain_to_writer() with writers that...
### Problem I experimented with setting transceivers to sendonly like this: ```rust for transceiver in peer_connection_offer.get_transceivers().await { transceiver.set_direction(RTCRtpTransceiverDirection::Sendonly).await; } ``` I do the necessary renegotiation, but (for simplicity) i have...