Philipp Oppermann

I'll go ahead and close this because I think this has been answered. Let me know if you still have issues.

Some nodes seem to exit with a `-1` return value. What is the cause for that? > [c node] received unexpected event: 2 Event type `2` is an `InputClosed` event....

Could you share the full output from your `out` file as well please? I tried to run your example code but I don't see any errors apart from some "stream...

I opened https://github.com/dora-rs/dora/pull/510 to make non-UTF8 output from nodes non-fatal. This way, `stdout` stays open and no `SIGPIPE` occurs. During my testing, this `SIGPIPE` was the reason that `node_C` failed...

@adamperkowski Feel free to submit a short project update to the "Other Projects" section for the next newsletter: https://github.com/rust-osdev/homepage/pull/228

Only C uses null-terminated strings, all other languages (including C++) use length-terminated strings. So I don't think that we should force all other languages to reallocate their `DataId`s just so...

The `const_fn` feature is using the compiler's unstable `const_mut_refs` feature, which is hopefully stabilized soon. See https://github.com/rust-lang/rust/issues/57349 for the current state. Unfortunately, we don't have any other way to create...

I pushed a commit to your branch to rename the `commands` module to `command`, in order to reduce the number of changes in the diff.

Our current behavior is that an event stream is closed as soon as all of its inputs are closed. This way, we enable dataflows to finish "naturally" without requiring a...

Some ideas how we could support this use case: - Add a some sort of dummy input to the source node that never fires. We could e.g. provide a built-in...