fix(test): handle TxnHashNotFound in db-compat test#435
Merged
Conversation
…tion Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
TxnHashNotFound in db-compat test
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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.
The db-compat test has been failing since #392 bumped bBockifier to v0.16.0-rc.0, which introduced a breaking change in
TransactionExecutionInfostruct serialization.The v1.6.0 test database contains traces in the old format that can no longer be deserialized, causing
trace_transactionto returnTxnHashNotFoundinstead of the trace data.This updates the test to accept
TxnHashNotFoundas a valid (expected) outcome for that call. The provider returnsNoneon deserialization failure as a backward-compatibility measure: