Thomas Eizinger
Thomas Eizinger
> [@thomaseizinger](https://github.com/thomaseizinger) Could you please provide a smaller, simpler workflow that reproduces the issue.Thanks. I don't unfortunately know exactly, what causes the problem. There are several other issues linked to...
For us, it doesn't really matter which linker we use. `rust-lld` works fine for us so we are likely going to stick with it. Reading the issue on the Microsoft...
Related: https://github.com/libp2p/rust-libp2p/issues/3390.
Related: https://github.com/libp2p/rust-libp2p/issues/2591.
I am almost certain that this would be fixed by https://github.com/libp2p/rust-libp2p/issues/2591 because that would move the IO off the main task which is typically the one running in `main.rs`.
FWIW, I've now implemented my own behaviour on top of `anyhow` that IMO has less foot-gun potential: https://github.com/firezone/firezone/pull/10966
> I'm keen to do the migration from the Swift Makefile as a follow-up, as it would be way more maintainable. Yeah good shout. The current problem I am facing...
I've been working on a sans-io desgined networking application for two years now (https://github.com/firezone/firezone) and my learning from that is, you usually want to decouple your IO from your state...
Relevant discussion happening here: https://github.com/libp2p/rust-libp2p/discussions/3411.
Cross-referencing a discussion around backpressure: https://github.com/libp2p/rust-libp2p/discussions/4585.