Add debug scenarios for ethui MCP demo - #106
Open
DavideSilva wants to merge 13 commits into
Open
Conversation
…verts Rename VaultToken -> DepositToken (on-chain ERC20 name/symbol unchanged) so Vault.token()'s generated hook no longer collides with the token contract's own base hook, eliminating the need for a custom getHookName policy in wagmi.config.ts. Re-deployed and re-pinned DepositToken/Vault addresses. Also tighten the three inverted revert tests (Vault, OwnedRegistry, SixDecimalToken) to assert the specific revert error instead of a bare vm.expectRevert(), so a scenario silently turning into a different bug would be caught.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
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.
Adds a
/bugsroute group with deliberately broken pages, each backed by a realcontract on anvil. Purpose: demo an agent connected to ethui over MCP diagnosing
failures from live chain state — not from reading source.
Governing constraint: no scenario is diagnosable from source alone. Where the bug
does live in source (decimals, allowance), the code reads as idiomatic and a
competing explanation exists that only on-chain state rules out.
Scenarios
/bugs/stale-addresseth_getCodereturns0x/bugs/access-controlOwnedRegistryowner is bob/bugs/decimalsERC20InsufficientBalancewith absurd numbersparseEther/bugs/allowanceVault.depositrevertsapprovebeforetransferFromAlso in here
contracts/bugs/—DepositToken,OwnedRegistry,SixDecimalToken,Vaultcontracts/scripts/BugsDeploy.s.sol+scripts/eth-deploy.shwiringRawErrorcomponent: renders the raw error and walks.cause, so pages showwhat failed without explaining why. Handles non-Error terminal causes and
synchronous
parseEtherthrows.no bare
vm.expectRevert().docs/superpowers/