Skip to content
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

Copilot should not use the code from the workspace to answer the query #4227

Open
wasertech opened this issue Jan 21, 2025 · 1 comment
Open
Assignees

Comments

@wasertech
Copy link

wasertech commented Jan 21, 2025

Type: Bug

User: Let's make a project to do this and that in a particular way.
Assistant: does this (but not really that - maybe because that almost exists already but not really -)
User: tests this and updates it slightly
User: "@workspace Ok this part of the code is fine, now let's make that like I mentioned."
Assistant: Literally replies with the code of the workspace
User: That's what I have already... you should not do that.

Extension version: 0.23.2
VS Code version: Code 1.96.3 (91fbdddc47bc9c09064bf7acf133d22631cbf083, 2025-01-09T18:14:09.060Z)
OS version: Linux x64 6.11.11-1-MANJARO
Modes:

A/B Experiments
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805:30301674
binariesv615:30325510
vsaa593:30376534
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
2i9eh265:30646982
962ge761:30959799
pythonnoceb:30805159
pythonmypyd1:30879173
h48ei257:31000450
pythontbext0:30879054
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
dsvsc021:30996838
dvdeprecation:31068756
dwnewjupyter:31046869
2f103344:31071589
nativerepl1:31139838
pythonrstrctxt:31112756
nativeloc1:31192215
cf971741:31144450
iacca1:31171482
notype1:31157159
5fd0e150:31155592
dwcopilot:31170013
stablechunks:31184530
6074i472:31201624
dwoutputs:31217127
hdaa2157:31222309
copilot_t_ci:31222730

@vs-code-engineering vs-code-engineering bot added the triage-needed Issues needing to be assigned to the prospective feature owner label Jan 21, 2025
@wasertech
Copy link
Author

Tbh my query was very difficult to begin with due to it complexity and the environment it was emitted. It managed this real fine, witch was to write a smart contract in rust and this to use an obscure framework on GitHub for the FE btw. Already had a dummy FE in the workspace.

@aeschli aeschli assigned mjbvz and unassigned aeschli Jan 22, 2025
@vs-code-engineering vs-code-engineering bot removed the triage-needed Issues needing to be assigned to the prospective feature owner label Jan 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants