WIP Shadow test ai#1803
Draft
lispc wants to merge 57 commits into
Draft
Conversation
…d in current code base)
Update stuffs Update intros purge files purge files
+ more defensive instruction + prune file being added by mistake
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Add complete documentation and automation for shadow coordinator + local prover setup to replay production mainnet tasks without interfering with live system. Includes: - docs/shadow-testing/README.md: full architecture, setup steps, troubleshooting - scripts/shadow-testing/setup.sh: one-command postgres/coordinator/prover setup - scripts/shadow-testing/import-production-data.sh: export from prod RDS to shadow DB - scripts/shadow-testing/fetch-l2-blocks.py: populate l2_block table from RPC - scripts/shadow-testing/configs/*.json: coordinator and prover config templates - scripts/shadow-testing/.env.example: environment variable template - scripts/shadow-testing/QUICKSTART.md: one-page quick reference - AGENTS.md: add shadow testing section with links All sensitive credentials (DB passwords, auth secrets) use environment variables or .env file. No hardcoded secrets in committed files.
Add a DryRun config option to the sender module. When enabled: - Transactions are simulated via eth_call instead of broadcast - pending_transaction table is not populated (avoids DB pollution) - Nonce is still incremented to simulate real behavior - Contract revert errors are propagated This allows testing rollup-relayer transaction construction (finalizeBundle, commitBatch, etc.) without spending gas. Includes: - SenderConfig.DryRun bool field - sendTransactionToMultipleClients dry-run logic - Skip pending tx insert/delete in SendTransaction when dry-run - rollup-relayer-dryrun.json config template - README update documenting the feature
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Purpose or design rationale of this PR
Describe your change. Make sure to answer these three questions: What does this PR do? Why does it do it? How does it do it?
PR title
Your PR title must follow conventional commits (as we are doing squash merge for each PR), so it must start with one of the following types:
Deployment tag versioning
Has
tagincommon/version.gobeen updated or have you addedbump-versionlabel to this PR?Breaking change label
Does this PR have the
breaking-changelabel?