Nico Flaig

Results 147 issues of Nico Flaig

Current openapi spec is invalid, see [validation result](https://validator.swagger.io/validator/debug?url=https%3A%2F%2Fethereum.github.io%2Fbuilder-specs%2Freleases%2Fv0.4.0%2Fbuilder-oapi.json). See https://github.com/ethereum/beacon-APIs/pull/421 for more rational.

### Motivation Initial discussion around this has started in https://github.com/ChainSafe/lodestar/issues/5128 to provide first-class support for SSZ in both request and response bodies but besides that, there are plenty of other...

meta-breaking-change

**Motivation** Motivation from https://github.com/ChainSafe/lodestar/pull/6776 to only skip ssz_static tests associated to missing type instead of all ssz_static tests. **Description** - add separate `it`-statement to assert that type is defined -...

### Describe the bug There is a validator monitor error in the slot right before first epoch transition ``` [cl-1-lodestar-nethermind] May-15 13:55:00.025[chain] error: Error on validator monitor onceEveryEndOfEpoch slot=31 -...

meta-bug

**Describe the bug** Noticed that Nimbus BN does not check the content type of the request body and just tries to deserialize it, causing strange errors. E.g. Error on Lodestar...

## Description Noticed that Lighthouse does not check the content type of the request body and just tries to deserialize it, causing strange errors. E.g. Error on Lodestar when trying...

HTTP-API

**Motivation** This flag is useful to quickly spin up or node on any network for testing / development and different users have asked for something like this. **Description** Unhide execution...

**Motivation** Closes https://github.com/ChainSafe/lodestar/issues/6611 **Description** Add warning log if primary beacon node is unhealthy Related to https://github.com/ChainSafe/lodestar/pull/6415

**Motivation** - https://github.com/ethereum/beacon-APIs/pull/442 **Description** `getHealth` returns 206 status code if EL is syncing / optimistic Closes https://github.com/ChainSafe/lodestar/issues/6664

**Motivation** We are pretty silent about the execution client being offline after the initial error. The logs just show that the node is stalling and not updating head but we...