-
-
Notifications
You must be signed in to change notification settings - Fork 69
fix(copilot): fixes from testing and integration #131
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
Open
theblazehen
wants to merge
9
commits into
Mirrowel:feature/copilot-provider
Choose a base branch
from
theblazehen:copilot-fixes
base: feature/copilot-provider
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
cae6872
fix(copilot): add credential setup and management flow
theblazehen b0c1aab
fix(copilot): fallback to login when email is null
theblazehen 0fb0f15
fix(copilot): return provider-prefixed models in model list
theblazehen 4ad36fb
feat(copilot): expand default model catalog to current provider set
theblazehen 8fa837e
fix(copilot): read credential_identifier in custom completion path
theblazehen 2eccf43
fix(copilot): await streaming handler in completion path
theblazehen 34b0490
fix(copilot): remove xhigh alias and stream delta compatibility
theblazehen 73ff3c9
fix(copilot): avoid ResponseNotRead when logging stream errors
theblazehen 229257e
fix(copilot): use centralized get_oauth_dir() instead of hardcoded Pa…
theblazehen 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.
Using
id(creds)for an in-memory lock key is clever, but be aware that it might lead to redundant locks if thecredsdictionary is copied or recreated (e.g., during serialization/deserialization cycles). If the credentials have a unique identifier like an email, that might be a more stable key.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.
Fair point —
id()can be recycled if the dict gets garbage collected and recreated. In practice the in-memory path only triggers for env-based credentials which are long-lived singletons, but using the email from_proxy_metadatawould be more robust. Open to changing if preferred.