Pieces Copilot is not working in VS Code

[PawanPawar11]

Software

VS Code

Operating System / Platform

Windows

Your Pieces OS Version

10.1.4

Early Access Program

• Yes, this is related to an Early Access Program feature.

Kindly describe the bug and include as much detail as possible on what you were doing so we can reproduce the bug.

I recently downloaded the Pieces VS Code extension, and when I tried to run it, it isn’t generating any output. I checked tutorials on YouTube, and I am following the same process as the instructor, but the extension is still not working.

[caleb-at-pieces]

Hey @PawanPawar11 we are currently tracking an issue that is causing the Copilot to fail on startup on windows devices. It would be very helpful for us if you could hop on a call and have a live debugging session! You can schedule here: https://calendar.google.com/calendar/appointments/schedules/AcZssZ3IijT1qgm0GgFeIllIuyy5ehWktuYQiPI6jegH4HlNGApAOMMVPiWCcoj_2aPfvgUiDmHHKcQE

Regardless, here is some information that will be useful for us to find the root cause of this issue:

• Please send me your logs, they are present within your documents folder: Documents\com.pieces.os\production\Support\logs
• What version of windows are you running?
• Are you on an insider build of windows?
• What version of Pieces OS do you have? Can you try this out on the latest version?
• What version of the VS Code extension are you running?

[PawanPawar11]

1. I have attached the log file as a text file. 2. Windows Version: "Windows 10 Home Single Language" 10.0 (Build 22631) 3. Yes, I am on an insider build of Windows. 4. Pieces OS Version: Pieces OS 10.1.5, which is the latest version. 5. VS Code Extension Version: v1.18.0, which is the latest version. Let me know if any additional information is needed.

On Fri, Aug 30, 2024 at 8:16 PM Caleb Anderson ***@***.***> wrote: Hey @PawanPawar11 <https://github.com/PawanPawar11> we are currently tracking an issue that is causing the Copilot to fail on startup on windows devices. It would be very helpful for us if you could hop on a call and have a live debugging session! You can schedule here: https://calendar.google.com/calendar/appointments/schedules/AcZssZ3IijT1qgm0GgFeIllIuyy5ehWktuYQiPI6jegH4HlNGApAOMMVPiWCcoj_2aPfvgUiDmHHKcQE Regardless, here is some information that will be useful for us to find the root cause of this issue: - Please send me your logs, they are present within your documents folder: Documents\com.pieces.os\production\Support\logs - What version of windows are you running? - Are you on an insider build of windows? - What version of Pieces OS do you have? Can you try this out on the latest version? - What version of the VS Code extension are you running? — Reply to this email directly, view it on GitHub <#379 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A2ADEK6MKDODP6WWT73VGLDZUCAT7AVCNFSM6AAAAABNAFQN4GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMRRGQ4TANBUHE> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[D] 2024-08-31T16:18:17.314901 Starting OS_Server! [D] 2024-08-31T16:18:17.314901 Starting EnvConf [D] 2024-08-31T16:18:17.314901 Starting DeploymentInfo [D] 2024-08-31T16:18:17.319897 Number: 112 [D] 2024-08-31T16:18:17.319897 Tag: 10.1.4 [D] 2024-08-31T16:18:17.319897 Branch: 10.1.4 [D] 2024-08-31T16:18:17.319897 SHA1: 89a247a9a8146624793ddc49185dc2308ce2dc00 [D] 2024-08-31T16:18:17.319897 WinDeployType: msix [D] 2024-08-31T16:18:17.319897 Channel : production [D] 2024-08-31T16:18:17.319897 Process ID: 6556 [D] 2024-08-31T16:18:17.319897 Copying the vocab file to the data directory [D] 2024-08-31T16:18:17.319897 Successfully copied the vocab file [D] 2024-08-31T16:18:17.319897 Starting OS [D] 2024-08-31T16:18:17.320903 Starting OS [D] 2024-08-31T16:18:17.329898 Starting UI [D] 2024-08-31T16:18:17.330903 UI#builder, hasData: false, hasError: false [D] 2024-08-31T16:18:17.330903 stateStream#onListen [D] 2024-08-31T16:18:17.330903 OS#boot [D] 2024-08-31T16:18:17.330903 OS#attach [D] 2024-08-31T16:18:17.620022 Logging to file: C:\Users\Hp\Documents\com.pieces.os\production\Support/logs/log-08312024.txt [D] 2024-08-31T16:18:17.624020 Created our Tagify Files Locally. [D] 2024-08-31T16:18:17.624020 User added tagify files now exist. [D] 2024-08-31T16:18:17.637018 OS#attempt to shutdown qdrant [D] 2024-08-31T16:18:18.648589 OS#successfully shutdown qdrant [D] 2024-08-31T16:18:18.654593 OS#totalTime: 1324695 [D] 2024-08-31T16:18:18.656591 OS#onBooted [D] 2024-08-31T16:18:18.656591 OS#port: 1000 [D] 2024-08-31T16:18:18.660591 UI#builder, hasData: true, hasError: false [D] Setting WinToast Dismissed Callback [D] 2024-08-31T16:18:21.650633 OS#attempt to boot qdrant [D] 2024-08-31T16:18:23.274120 OS#successfully booted qdrant [D] 2024-08-31T16:18:31.618922 OS#machine learning models loaded successfully [D] Checking for updates for MSIX Side-loaded installations [D] [34m MsixUpdaterApi: Attempting to check for an updates [0m [D] [34m MsixUpdaterApi: There was an error in the response: error: [0m [D] Sentry Error Event: 688917f1c0934cfeaeea09ac928e0c5b [D] Callback event for toast: getSupport [D] Callback event for toast: getSupport [D] 2024-08-31T16:23:04.953421 0:00:00.007664 GET [200] /.well-known/version [D] 2024-08-31T16:23:09.924272 0:00:00.000205 GET [200] /.well-known/version [D] 2024-08-31T16:23:14.923963 0:00:00.000114 GET [200] /.well-known/version [D] 2024-08-31T16:23:19.923964 0:00:00.000143 GET [200] /.well-known/version [D] 2024-08-31T16:23:24.923757 0:00:00.000435 GET [200] /.well-known/version

[PawanPawar11]

I checked this morning to see if the Pieces code extension was working, and it turns out it is. However, I’m not sure why it stopped working earlier or why it’s working now. I still have an issue with the Pieces desktop version regarding its font size; you can review my issue under number #378. I was wondering if I could hop on a call with you to discuss this, as the VS Code extension problem is now resolved.