Philipp Oppermann
Philipp Oppermann
With the new event stream design merged in #162, all nodes should listen for incoming events, even if they don't expect inputs. Nodes that don't do this will be killed...
Thanks a lot for the detailed explanation! Let me try to summarize the features that you would like to see in dora: - request/reply communication - goal: receive the reply...
We don't have a way to limit the queue length yet, but we agree that such a feature is definitely needed. The question is whether we should signal to the...
Thanks a lot for the explanation, this is very useful! I think the main priority for dora is the history/depth/queue length setting. We can look into the other QoS options...
Great to hear that, thanks! For now we just check the running processes, so we have a workaround.
We don't have plans to implement such a multithreading mechanism in dora right now. The main advantage of the current single-threaded design is that the `on_input` function has exclusive access...
Thanks for reporting! > Ok, I submitted the related PR You're talking about https://github.com/dora-rs/dora-drives/pull/55, right? Regarding the error: Did you see any warnings in the logs? There are some situations...
Ok good. And the default log level is `warn`, right? Then it sounds like the file handle number is the issue.
> The default is the same as Tokio tracing default which is `error`. We can change it to warn. This would be a good idea in my opinion. We're using...
@meua Thanks a lot for the info!