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.
Calling
Bifrosting
/index
endpoint to create the index MV in friggBehavior Change Needed
The current behavior leaves a lot to be desired:
Problem: I can't actually put up a spinner for "all the queries that completed, and missed, because in the future they will re-fire". So, users will see lots of blank no spinner, wondering "wait.. did it work?!"... snap the data shows up.
Proposal: if we block the
commit
of/create_changeset
endpoint until the new change set's index is created, then we get no ugliness.. no 404s, no "can't spinner" problem—because I can absolutely show a spinner for "I did an HTTP POST to/create_changeset
and it hasn't returned yet". This doesn't "lengthen" the wait time for users—in the current behavior where they get redirected immediately, they can't see anything anyway.