Michael Sproul

Yeah it should be. We're fighting a battle with our HTTP library to get it not to morph 404s into 405s. The tracking issue for that is here: https://github.com/sigp/lighthouse/issues/3112

I think this is an instance of this bug https://github.com/sigp/lighthouse/issues/3011, which I've been trying to solve on and off for a while. The strangest thing about it is that it...

Added some debugging tools in this PR which might help us get an idea of what happened: https://github.com/sigp/lighthouse/pull/3511

Do you have an ARM CPU? I just downloaded the v2.5.1 binary and it's definitely an x86-64 binary: ``` $ tar xf lighthouse-v2.5.1-x86_64-unknown-linux-gnu.tar.gz $ file lighthouse lighthouse: ELF 64-bit LSB...

Have you inquired with Teku about this? It looks like it might be a discrepancy in how we define the `sync_distance` in the `/eth/v1/node/syncing` endpoint. Lighthouse tries to use the...

> What I haven't found out yet is why this error only appears during the doppelganger protection phase. I've seen several reports now of users seeing this even when they're...

Ah, I wasn't aware that a decision had been made to include constants in the spec endpoint. As in, I hadn't seen this paragraph before: > Retrieve specification configuration used...

It looks like you've rolled your changes from #3366 into this PR, which is fine, we can review it all in one go. I'll close #3366 for now seeing as...

@tobisako Yeah this issue is the cause of that. So Teku is usable if you specify the network manually?

It may be that we want to avoid `and_then` for our handlers and instead use `then`. The `warp` docs state: > Rejections are meant to say “this filter didn’t accept...