Skip to content

Conversation

mjfh
Copy link
Contributor

@mjfh mjfh commented Sep 8, 2025

No description provided.

mjfh added 7 commits September 5, 2025 17:36
details
  This tool wraps and runs the `nimbus_execution_client` while
  tracing and capturing state data.
details
  Currently only for dumping capture data as logs
details
  This tool wraps and runs the `nimbus_execution_client` with the
  sync scheduler partially superseded by a capturing state data
  replay facility.
@mjfh mjfh requested a review from tersec September 8, 2025 08:08
mjfh added 14 commits September 16, 2025 09:55
why
  No need for extra command line parsing stuff
details
  No need to prefix capture type names by `Trt`, so removed
  Simplify reader switches by using template+mixin
  Using static table for pretty printing capture record labels
…ures

why
  Contrary to RLP which was not fully reliable at the time of defining
  the capture record layout, JSON is fully capable of handling `Opt[]`
  constructs.
why
  The layout of the `ReplayMsgRef` sub-structures mirrors that of the
  `ReplayPayloadRef` sub-structures. So the latter sub-structures have
  been replaced by the former ones.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants