- 
                Notifications
    
You must be signed in to change notification settings  - Fork 147
 
Beacon sync trace replay test tools #3642
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
          
     Closed
      
      
    
                
     Closed
            
            
          Conversation
  
    
      This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
      Learn more about bidirectional Unicode characters
    
  
  
    
    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.
              
                    arnetheduck
  
              
              reviewed
              
                  
                    Sep 8, 2025 
                  
              
              
            
            
              
                    arnetheduck
  
              
              reviewed
              
                  
                    Sep 8, 2025 
                  
              
              
            
            
              
                    arnetheduck
  
              
              reviewed
              
                  
                    Sep 8, 2025 
                  
              
              
            
            
              
                    arnetheduck
  
              
              reviewed
              
                  
                    Sep 8, 2025 
                  
              
              
            
            
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.
    
  mjfh 
      added a commit
      that referenced
      this pull request
    
      Oct 23, 2025 
    
    
      
  
    
      
    
  
history
+ Docu for setting up network tunnel for testing
+ Adjust to changed main API
+ Remove `ReplayMsgRef` types and use `ReplayPayloadRef` instead
  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.
+ Re-factor `ReplayRef` inheritable by `ReplayRunnerRef`
+ Replace bit-mask controlled optional capture fields by `Opt[]` structures
  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.
+ Simplify/prettify code
  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
+ Refactor capture records for JSON format read/write
+ Using gunzip from updated `nim-zlib` package
+ Use `confutils` for command line options management
+ why
    No need for extra command line parsing stuff
+ Fix copyright years
+ Provide command line capture replay tool
  details
    This tool wraps and runs the `nimbus_execution_client` with the
    sync scheduler partially superseded by a capturing state data
    replay facility.
+ Update replay framework for full capture replay
+ Provide command line capture inspection tool
+ Provide capture inspection framework, part of replay
  details
    Currently only for dumping capture data as logs
+ Provide command line tracer tool
  details
    This tool wraps and runs the `nimbus_execution_client` while
    tracing and capturing state data.
+ Provide tracer framework with intercepting syncer session handlers
    
    
  mjfh 
      added a commit
      that referenced
      this pull request
    
      Oct 23, 2025 
    
    
  
| 
           Superseded by #3790  | 
    
  
    Sign up for free
    to join this conversation on GitHub.
    Already have an account?
    Sign in to comment
  
      
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
No description provided.