Ecosyste.ms: Timeline
Browse the timeline of events for every public repo on GitHub. Data updated hourly from GH Archive.
github-actions[bot] created a comment on a pull request on status-im/nimbus-eth2
## Unit Test Results 12 files ±0 1 810 suites ±0 54m 39s [:stopwatch:](https://github.com/EnricoMi/publish-unit-test-result-action/blob/v1.20/README.md#the-symbols "duration of all te...
kdeme created a review comment on a pull request on status-im/nimbus-eth2
Added it under the `debug` namespace for now. Although I realize that `debug` is not actually purely a list of debug endpoints as the state one is used by users for trusted node sync.
kdeme created a review comment on a pull request on status-im/nimbus-eth2
I added this as it seems to be added always (?), even though I can't think of any use for it in the specific case of `historical_summaries`. (Perhaps if the `BeaconState` amount of fields grows > 3...
kdeme created a review comment on a pull request on status-im/nimbus-eth2
I opted for JSON and SSZ, as that is what the debug state endpoint does and also because I was using the SSZ version already in our `portal_bridge`. I'm not sure what the convention is, or if t...
kdeme opened a draft pull request on status-im/nimbus-eth2
Add REST endpoint to retrieve historical_summaries
In draft currently as it is not in spec. Needs to be accompanied still with a proposal for beacon REST API specifications. The idea is that `historical_summaries` is very useful for verifying if...
kdeme created a branch on status-im/nimbus-eth2
historical-summaries-endpoint - Nim implementation of the Ethereum Beacon Chain
tersec pushed 1 commit to testing status-im/nimbus-eth2
- json-ser (#6674) bump for overlong array crash fix 40f2acc
cheatfate created a review comment on a pull request on status-im/nimbus-eth2
Fixed in https://github.com/status-im/nimbus-eth2/pull/6515/commits/fe6452e7b2c0ebd985ffcde3aca35c6303723b2e
cheatfate pushed 1 commit to hybrid-sync status-im/nimbus-eth2
- Address review comments on state as argument. fe6452e
tersec pushed 1 commit to unstable status-im/nimbus-eth2
- json-ser (#6674) bump for overlong array crash fix 40f2acc
arnetheduck opened a pull request on status-im/nimbus-eth2
json-ser
bump for overlong array crash fix
arnetheduck created a branch on status-im/nimbus-eth2
json-ser-fix - Nim implementation of the Ethereum Beacon Chain
agnxsh pushed 1 commit to pdsync status-im/nimbus-eth2
- eliminate block header check to make sync work f4502b5
tersec created a review comment on a pull request on status-im/nimbus-eth2
The only use of `BeaconState` I can find in the file is https://github.com/status-im/nimbus-eth2/blob/f54a0366abfba26c7694fad1e14350d19aa0a228/beacon_chain/spec/signatures_batch.nim#L232-L239 a...
tersec created a comment on a pull request on status-im/nimbus-eth2
Sure, `testing` branch updated but like to keep `unstable` clear of anything risky for 3 or 4 days after, ideally until actual release, in case small fixes need to go into `testing` with minimal di...
arnetheduck created a comment on a pull request on status-im/nimbus-eth2
this will need a look to see that deposits syncing is still fine - should be, because the client updates to json-rpc are mostly harmless, but still
arnetheduck created a comment on a pull request on status-im/nimbus-eth2
this one is a bit risky, can wait til the next release
tersec created a comment on a pull request on status-im/nimbus-eth2
My concern is that PeerDAS won't, in fact, be in PectrA/Pectra, and as such this will trigger for end-users when the first of Sepolia or Holesky forks. Want to keep this out of `unstable` until tha...
jurijus01 opened an issue on status-im/nimbus-eth2
Quit if system clock is wrong
**Is your feature request related to a problem? Please describe.** Spent few hours on Discord getting help about peculiar edge case when block sync approached 93% and then started decreasing, havin...
yakimant opened an issue on status-im/nimbus-eth2
ncli_db: incorrect era file generated
**Describe the bug** `exportEra` generated an incorrect era file. `verifyEra` is failing with ``` Checking: /data/era/mainnet-00781-6e8fa554.era Invalid block signature ``` You can file the file...