Skip to content
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

don't touch send flow this time #1537

Conversation

AloeareV
Copy link
Contributor

Instead of messing up send flow when this rescan doesn't update obsolete metadata, only add the check to the rescan flow and not the send flow.

@AloeareV AloeareV force-pushed the second_attempt_rescan_old_outgoing_output_indexes branch from 74cb27a to c0b35bd Compare November 19, 2024 19:17
@zancas
Copy link
Member

zancas commented Nov 20, 2024

I see that this constrains extension of output indexes to only be from confirmed transactions. I understand this to exclude data from "the send flow" is that how to interpret the title of this commit?

@zancas zancas merged commit 24a4097 into zingolabs:dev Nov 20, 2024
17 checks passed
@AloeareV
Copy link
Contributor Author

I see that this constrains extension of output indexes to only be from confirmed transactions. I understand this to exclude data from "the send flow" is that how to interpret the title of this commit?

No, the original attempt at this added the new code inside get_spendable_note_ids_and_values, which was called during the send flow as well as inside unindexed_records. The reason we only check confirmed notes, is that this code is only called when we read old transactions from the wallet, that are missing information. Unconfimed notes don't need to be rescanned (they're too new to be able to hit this clause, and even if they could they're also gonna be rescanned on confirmation anyway.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants