-
Notifications
You must be signed in to change notification settings - Fork 183
feat(solana-indexer) PR 8: wire the decoder to the persistence seam #4676
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
squadgazzz
wants to merge
5
commits into
solana-indexer/PR7.3-interface-parser
Choose a base branch
from
solana-indexer/PR8-persist
base: solana-indexer/PR7.3-interface-parser
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 2 commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
dd95347
feat(solana-indexer): wire the decoder to the persistence seam
squadgazzz 77a8d05
test(solana-indexer): fold the decode-wrap and revert cases into one …
squadgazzz a4d7a09
refactor(solana-indexer): use Slot for slot arguments and match aucti…
squadgazzz 16d35c5
fix(solana-indexer): dead-letter transaction updates that arrive with…
squadgazzz ec232d1
fix(solana-indexer): make every dead-lettered transaction diagnosable…
squadgazzz 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
Oops, something went wrong.
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.
The revert guard treats a missing
metaas "not reverted" and falls through to decoding, whereas a few lines down (post_token_balances, L138–142) a missingmetais handled defensively viaunwrap_or_default(). That's an inconsistency in how the two paths reason aboutmetabeing absent.If
metacan ever beNoneon a transaction update, we'd emit state-changing events for a transaction whose success we can't actually confirm — the opposite of the safety property this guard is establishing (spec §4). In practice Yellowstone always populatesmetafor tx updates, so this is likely defensive-only, but if that invariant holds it would be cleaner toexpect/error on the absent case; if it doesn't hold, a missingmetaarguably should skip (or dead-letter) rather than decode. Worth a one-line comment stating which it is.