jul-sh

Thanks for the heads up, I'll look into it. > @jul-sh is it worth considering running this also pre-merge, without actually writing the provenance anywhere (dry run), so that at...

Issue 1 & 4 could be resolved relatively nicely by refactoring the signature of the `handshaker.next_step`. Currently it returns: `anyhow::Result`. It uses a nested Result and Option, to effectively express...

The ideal structure would probably be: For each client, the only state that is maintained on the server is a transcript of messages (equivalent of the current `Transcript` inside the...

Sorry for the late update. This issue consists of two tasks, the more impactful of which is done. - [X] the LRU cache track of sessions (done in #2743) -...

Thanks for raising the issue! In order to favor the simplicity and maintainability, my intuition would be to take the pragmatic way of looking at the larger concern. In essence...

cc @tiziano88 @ipetr0v

> @jul-sh Any update to @CasperN comments? cargo test doesn't ordinarily test no_std compatibility in dependency of libraries. This is likely why it looks fine there. Ref https://blog.dbrgn.ch/2019/12/24/testing-for-no-std-compatibility/ At a...

> @jul-sh Any update to this? Haven't looked into yet, but should be able to in mid September

This is blocked by https://github.com/bbqsrc/thiserror-core2/pull/3 getting merged upstream, as flatbuffer depends on that crate. It needs (very minor) changes to ensure no_std compatibility. Unfortunately no news from the maintainer so...

@CasperN Could you approve running the workflows? Attempted the CI integration. Would be surprised if it works right away (Windows runs especially might be tricky), but would be good to...