-
Notifications
You must be signed in to change notification settings - Fork 6
Tracing support #350
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
Tracing support #350
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me let's get this stuff merged.
Could you also mark here #265 all the cheatcodes that should now work.
| None | ||
| } | ||
| // Remove duplicate acceses in storage_recorder | ||
| fn revive_remove_duplicate_account_access(&self, _state: &mut crate::Cheatcodes) {} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can you explain why is this needed ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
duplicate placeholder records are added in Inspector::call_with_executor/Inspector::create_common this ideally needs to be refactored and moved to strategies, but i'd rather wait and see how zk-foundry does it
…into pkhry/tracing
Description
pvmmode. #327, [Forge test][Tracing] Implement base tracers #328expect_emit,expect_revert,recordLogsandAccountAccessesNotes
suddenDuplicateContracterrors when using with latest master