fix: Make sure txs are eventually marked as confirmed or orphaned #1102
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.
Related to #889
Depends on
Description
This branch makes sure that we eventually handle marking all unconfirmed txs as either confirmed or orphaned. Admittedly, I don't know why this is an issue in the first place (I've confirmed it isn't related to the server being restarted) but this should at least catch anything weird that isn't sorted out in the first pass.
Test plan
Make sure everything is running smoothly. Then perhaps try adding a new row manually into the Transaction db for a tx that doesn't exist and see that the system marks it as orphaned after 30 minutes.