Thread panic

[radicle-dev]

Thread panic

[kim]

I'm sure this was fixed upstream, can't find where at the moment. Iow, should go away with newer quinns.

[FintanH]

This looks like there was a panic deep in the bowels of the networking. Unfortuately, there's not enough information to go off of here. There's not much to do unless you can provide more information on this, for example, the logs before the stack trace, which commit SHA you're using for deploying the seed, etc.

[xni]

Yep, I found how to reproduce it:

nc -u 95.216.68.43 12345
abc

and the version is:

f1462b92a06ef65ec4b65201e9801473a41b4ee3 (HEAD)

some lines before the backtrace:

thread 'tokio-runtime-worker' panicked at 'range end index 8 out of range for slice of length 3', /git/checkouts/quinn-572d2e5812b43165/babb07b/quinn-proto/src/packet.rs:517:46
thread 'tokio-runtime-worker' panicked at 'called `Result::unwrap()` on an `Err` value: "PoisonError { inner: .. }" /git/checkouts/quinn-572d2e5812b43165/babb07b/quinn/src/endpoint.rs:215:42

[xla]

If you send messages that the networking doesn't expect like in your example above it will crash. It's not ideal but expected behaviour at this point.

[xni]

I understand that the issue may be in the quinn module, but still... crashing on unknown packet is weird

[xla]

It is, but the code that currently causes that is on the way out and we are rolling out an updated network stack. We don't have the capacity or the incentive to invest any more time in the current code and are working hard on the updated stack. Thanks again for taking the time to report this issue.