-
Notifications
You must be signed in to change notification settings - Fork 6k
fix (acp): Refresh provider when session working directory changes #9883
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
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
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.
When this request targets a persisted session that is not currently registered in
self.sessions,get_session_agentfalls back to activating the session (viaactivate_acp_sessioninserver.rs) just to refresh a provider. In that context there is no live provider to refresh, so changing metadata for an inactive/listed session can unexpectedly spawn provider subprocesses and extensions (and then recreate the provider again here), whereas the previous path only notified an already-active ACP session. Please only refresh the provider when an agent is already registered, and otherwise leave the persisted cwd update as a metadata-only operation.Useful? React with 👍 / 👎.
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.
The activation is intentional for the current desktop migration path: the UI can update cwd through ACP for a session originally created through REST, so absence from
self.sessionsdoes not mean “inactive/list-only.” We can change it when the migration is doneThere 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.
It makes sense that activation is intentional but in case
get_session_agentcreated an ACP provider (it callscreate_agent_locked), the newrestore_provider_from_sessioncall below will immediately create it again. So if CWD is updated and the session was not already active, then the ACP provider is created twice in a row.