Pieces app doesn't return response after prompting

[nbriggsrsi]

Software

Pieces OS, VS Code

Operating System

Windows

Your Pieces OS Version

8.0.0

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

Using various models, I will sometimes encounter an issue where after entering a prompt, Pieces returns nothing. It appears to read the prompt, shows the relevant files in a list below the prompt, and a message that says "Almost there" appears. But then both the relevant files and "Almost there" message disappears, and then it just seems to "give up."

I've had this happen with other models, but in this case, I was trying the Bison model. Also I've noticed when I get this message, I keep getting this message. Then all of a sudden, a day later in one case, it starts working again.

[caleb-at-pieces]

Couple things that will help us get to the bottom of this issue:

1. does restarting Pieces OS and / or VS Code resolve this issue?
2. when this issue occurs, do you also see the same issue in other integrations like the Desktop App?
3. Does this happen more often for specific models?
4. Were you doing anything else before this happened? Some exact steps to reproduce would be great!

[nbriggsrsi]

Let me try your suggestions, and I'll get back to you. I can tell you now that restarting VS Code does not solve the issue, and it seems to be happening mainly with the cloud models, which is strange. I have a GPT4 API key from my subscription and tried using that, and even that gives me the same result.

Changing to Mistral 7B CPU on-device seems to solve the issue though and it gave me some decent results too, which I'm happy about.

I'll keep playing with this and get you some exact steps to see if you can reproduce the error.

My hope also was that, like GPT4, it would have the ability to reach out online to read documentation to add to its context. Is there any way to achieve that? Just curious.

[caleb-at-pieces]

Let me try your suggestions, and I'll get back to you. I can tell you now that restarting VS Code does not solve the issue, and it seems to be happening mainly with the cloud models, which is strange. I have a GPT4 API key from my subscription and tried using that, and even that gives me the same result.

Excellent, thank you for the info. Let us know if you have some more details later.

My hope also was that, like GPT4, it would have the ability to reach out online to read documentation to add to its context. Is there any way to achieve that? Just curious.

Our Copilot does not currently have the ability to search the web however you are able to use websites as context in the VS Code extension as of the 1.13.0 release (about 8 days ago)

[caleb-at-pieces]

@nbriggsrsi @sunarkadeep

I have just had this happen to me within VS Code and I checked my developer tools console Help > Toggle Developer Tools and see this error message:

Can someone confirm this is the same error message they see in their logs?

[sunarkadeep]

@caleb-at-pieces how can I reach this? after Help > Toggle Developer Tools .....because then a window appears and there's too many things to look at....

[caleb-at-pieces]

@caleb-at-pieces how can I reach this? after Help > Toggle Developer Tools .....because then a window appears and there's too many things to look at....

You can do so like this too:

1. ctrl + shift + p for linux / windows or command + shift + p for macos to open command palette
2. search: 'Toggle Developer Tools'
3. select the first option to open developer tools.

Once the window opens, you must then click on the 'console' tab that is present on the header of the window to open the console and see logs.

[sunarkadeep]

okay so I did that but nothing sort of log as you posted appeared on mine.... what I got is just

[caleb-at-pieces]

okay so I did that but nothing sort of log as you posted appeared on mine.... what I got is just

Great, if you happen to encounter the same issue again please check and put the output here in this thread!

[sunarkadeep]

@caleb-at-pieces
so a quick update, the issue is still persistent....like the very first reply from the copilot in a new chat just appears and disappears...like really quickly....thus taking me back to the pieces copilot home page in the side panel...then the only way to access the conversation again is to either close and reopen vscode or close copilot from the side panel and reopen it.....and also in vscode console, there is no such error or issue statements...

and the problem with refreshing in pieces desktop app copilot is not there anymore...so just the vscode one is there

[caleb-at-pieces]

@sunarkadeep We should be releasing a change in the next version of the VS Code extension that will fix this. So hang tight for a bit and this problem should be resolved soon.

[sunarkadeep]

Great!

[sunarkadeep]

@caleb-at-pieces
okay so the response delay of copilot within vscode now seems to have been solved. I can finally see immediate response and it works just the way it should 👍