-
Notifications
You must be signed in to change notification settings - Fork 0
fix(scheduling): close seven ledger and authoring follow-ups from the MVP review #1255
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
Merged
Merged
Changes from all commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
057a616
fix(scheduling): bound offering capability and prerequisite lists at …
jeremi 2f1aa75
fix(scheduling-client): bound the offering selector before availabili…
jeremi 55e5a69
fix(scheduling): advance the claim revision when hold expiry closes it
jeremi 78e9333
fix(scheduling): release the duplicate key once the booking has passed
jeremi ca800c8
fix(scheduling): answer a close retry from the policy that governed t…
jeremi 89f0c14
fix(scheduling): re-check the policy against its window records at th…
jeremi 2466ed2
fix(scheduling): keep one supply identifier to one kind of supply
jeremi d1e0196
fix(scheduling-client): hold the offering selector to the policy grammar
jeremi c34c21e
fix(scheduling): read a close retry's terms from the claim, not the i…
jeremi 51de118
fix(scheduling): index the whole predicate the duplicate guard filters
jeremi File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
13 changes: 13 additions & 0 deletions
13
crates/registry-scheduling/migrations/0007_duplicate_lookup_index.sql
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,13 @@ | ||
| -- The offering-wide duplicate guard filters on three columns: the key the | ||
| -- caller sent, the offering the claim was made under, and whether the booking | ||
| -- it names is still ahead. Schema version 1 indexed the key alone, leaving the | ||
| -- other two to a recheck over every active claim carrying that key. A booking | ||
| -- stays 'active' once its time has passed, because the ledger publishes no | ||
| -- completion transition and nothing sweeps elapsed bookings closed, so the | ||
| -- rechecked set grows for the life of the deployment rather than with the | ||
| -- bookings a party currently holds. Index the whole predicate instead. | ||
| CREATE INDEX IF NOT EXISTS scheduling_claims_duplicate_lookup_idx | ||
| ON scheduling_claims(duplicate_key, offering, occupied_end) | ||
| WHERE state = 'active' AND duplicate_key IS NOT NULL; | ||
|
|
||
| DROP INDEX IF EXISTS scheduling_claims_duplicate_idx; |
Oops, something went wrong.
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.