Niklas Adolfsson

The `logging` is written to stderr AFAIK but the problem is that the backtraces such as panics are not logged there. So, I don't know how to do it without...

We could also incorporate [cargo-deny](https://github.com/EmbarkStudios/cargo-deny)

> I'm not sure we should worry about https://en.wikipedia.org/wiki/Year_2038_problem for now, the code will probably change by then. I'm not referring to the `2028 year problem`. I mean that a...

> What if a block timestamp is forged but still fits i32? This code can't catch this in any way. I was not talking about that just the difference between...

Ah I see the entire connector config is used then I guess

Hey @Tbaut tokio is the underlying async executor/threadpool that drives "async IO" to completion which is required by jsonrpsee for everything except for the wasm client. However with some conditional...

I suspect that the `substrate node` and `substrate archive` is using different versions, @kaisuki can you double check which versions you are using?

It's probably because `substrate` has been updated to jsonrpsee 0.14. You could try `cargo build --locked` or upgrade jsonrpsee

Hey, It indeed seems like a bug. Can you explain how you run your node such as behind a nginx proxy/load balancer or something similar? I have seen something similar...

right, it will be hard for me to try to reproduce that locally. do you have any idea how to reproduce this or any additional logs to share?