-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
Zed logs error for missing ~/.config/github-copilot (linux) #17831
Comments
Apart from the inline provider, there's also the AI chat. I suspect Zed looks at which providers you're signed into for the chat. |
This comment was marked as off-topic.
This comment was marked as off-topic.
Not currently preventing startup for me. No current lead on why that part differs for you. |
Yeah, looking at the code the GitHub Copilot Chat via the Assistant panel uses that file: zed/crates/copilot/src/copilot_chat.rs Lines 175 to 187 in 0f4ebdf
I was able to reproduce by removing my Thanks for reporting. |
I did some digging and I believe this is happening because we add a watch for zed/crates/copilot/src/copilot_chat.rs Lines 195 to 199 in f5124c2
If the Lines 524 to 525 in f5124c2
|
I believe this was fixed by: More info here If you are still seeing this in your logs with a current release, please comment with more details and I'm happy to reopen. |
Check for existing issues
Describe the bug / provide steps to reproduce it
settings.json
to disable GitHub Copilot, because I don't want the contents of my text editor sent to a 3rd party in the background.grep -rni copilot ~/.local/share/zed/logs/Zed.log
If copilot is properly disabled, why is it searching searching for it's config/API keys?
Environment
Zed: v0.152.3 (Zed)
OS: Linux Wayland gentoo 2.15
Memory: 31.3 GiB
Architecture: x86_64
GPU: AMD Radeon RX 570 Series (RADV POLARIS10) || radv || Mesa 24.1.6
If applicable, add mockups / screenshots to help explain present your vision of the feature
No response
If applicable, attach your Zed.log file to this issue.
No response
The text was updated successfully, but these errors were encountered: