Repository navigation
fix: validate sysvar data before refreshing the sysvar cache - #436
Merged
Aursen merged 1 commit intoOct 18, 2026
Merged
Conversation
`handle_sysvar` reset the sysvar cache and refilled it from the new account before checking that the data parses, so a rejected write still dropped that sysvar from the cache. after an invalid rent write the next transaction panicked at `lib.rs:1318` with `UnsupportedSysvar`. LiteSVM#20 checked first, LiteSVM#95 moved the check below the reset. i moved it back above, like the clock branch already does
Iamsohungrynow
force-pushed
the
fix/sysvar-cache-rejected-write
branch
from
October 17, 2026 13:21
af1ad7a to
0b57e27
Compare
Aursen
approved these changes
Oct 18, 2026
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
2 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.
set_accountwith invalid sysvar data returned an error but still wiped that sysvar from the cache, so after a bad rent write the next transaction panicked atlib.rs:1318. i now check the data before resetting the cache