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

Conceptualize how to deal with incompletely propagated bill data #195

Open
zupzup opened this issue Oct 29, 2024 · 0 comments
Open

Conceptualize how to deal with incompletely propagated bill data #195

zupzup opened this issue Oct 29, 2024 · 0 comments
Labels
enhancement Enhancement of existing code

Comments

@zupzup
Copy link
Collaborator

zupzup commented Oct 29, 2024

Currently, it's possible that one gets one of the two files (bill / bill keys) and then fails, because it expects the other to be there. The same goes for attachments on bills - the bill might be there, but not the attachments yet

In that case, we need to attempt to fetch (in the background - and retry) the missing file and somehow return to frontend, that we don't have all the data (yet).

@zupzup zupzup converted this from a draft issue Oct 29, 2024
@mtbitcr mtbitcr added the enhancement Enhancement of existing code label Nov 7, 2024
@zupzup zupzup changed the title Fix race-condition when fetching bill and bill keys Conceptualize how to deal with incompletely propagated bill data Nov 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Enhancement of existing code
Projects
Status: Todo
Development

No branches or pull requests

2 participants