-
-
Notifications
You must be signed in to change notification settings - Fork 34
feat(agents): consent approval sets registry handle (#1800 slice 7) #1826
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
Closed
Closed
Changes from all commits
Commits
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
WARNING: Unique index creation can abort
init()on existing databases with duplicate active handlesThis
CREATE UNIQUE INDEX IF NOT EXISTS ux_agent_active_handleruns unconditionally insideSCHEMAviaexecutescriptatinit()(base_store.py:38), and theWHERE status='active' AND handle!=''guard only excludes empty-handle rows. The earlier, unindexed version of this very feature (flagged by the prior review) could already persist two ACTIVE rows sharing a non-empty handle, so any database written in that window will fail the index build withIntegrityErrorand abortinit(), taking down the whole registry store on upgrade.Build this in a guarded migration that first detects/clears duplicate active handles (e.g. keep the earliest, rename or suspend the rest) before creating the index, so
init()cannot fail on pre-existing bad data. The test inTestPartialUniqueHandleIndexonly covers fresh DBs, not the upgrade path.Minor note (route agent_auth_requests.py:381): the
rollback()here is effectively a no-op becauseregister()already committed the pending row (agent_registry_store.py:424) — the real cleanup is thedelete()call. The surrounding comment is slightly inaccurate but harmless.