Make lookup_txos error instead of panic #116
Closed
Conversation
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
Collaborator
|
I believe these errors are likely happening due to a different reason, which was fixed by #89 and in particular by this commit: 5c8c785 With this fix the internal db should remain consistent and there should be no more "missing txo" errors, even if the backend node changes. We either have the tx in full, including its parents, or we don't. If the new node doesn't have it then it'll get evicted from electrs too. |
junderw
pushed a commit
to junderw/electrs
that referenced
this pull request
Oct 4, 2025
…history-ordering Fix address history tx ordering
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.
No description provided.