-
Notifications
You must be signed in to change notification settings - Fork 243
perf(vm): key the class cache on declaration height instead of load height #4029
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
Open
infrmtcs-agent
wants to merge
1
commit into
main
Choose a base branch
from
dat/bench-trace-block-txs
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
Oops, something went wrong.
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.
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.
This test reuses the class hash
0x3297a93c...2010ethatTestCallDeprecatedCairoandTestCallDeprecatedCairoMaxStepsalso use.CLASS_CACHEon the Rust side is a process-widestatic(vm/rust/src/state_reader/state_reader.rs:32), so it persists across every Go test in this binary — there's no reset hook between tests.Today this is safe only because those two other tests call the VM with
Header.Hash == nil(pending), so pervm/vm.go:328they resolve toBlockHeight::Pendingand never populate the cache for this hash. If a future test is added (or an existing one is edited) to call the VM with a non-pending header for this same class hash, it would silently pre-populateCLASS_CACHEwith adeclared_atthis test doesn't expect, andTestClassCacheKeyedOnDeclarationHeightwould start passing/failing based on test execution order rather than the behavior it's meant to verify.Since the assertions are already relative to
fetchesAfterFirstCallrather than absolute counts, this doesn't cause a current flake, but it's a footgun for future edits. Consider using a class hash that's unique to this test (or asserting/documenting the shared-cache dependency explicitly) so the test stays correct regardless of what other tests in the package do.Fix this →