@amanrs @Cursor Team. Any update on this bug?
For some added context:
For a number of previous versions, Copilot++ would inexplicably stop working temporarily only to suddenly start functioning again for no apparent reason. The ‘non-working’ state was very sporadic and didn’t last that long so I thought it was just a quirk of AI/network issues etc.
As of V0.33.4 the ‘non-working’ state would persist indefinitely and wouldn’t start working again until I have commented out some random lint errors. However just typing half a variable name would stop Copilot++ from working as the ‘half variable name’ was deemed to be a lint error etc.
I have now rolled back to V0.32.8 and Copilot++ is still quite temperamental. I’m now working with the ‘Copilot++ Output’ window open constantly so that I can instantly tell when Copilot++ has stopped working (i.e. it displays the ‘Error in streaming cpp’ log message). Then I have to go and search for any lint errors (red squiggles) in the file and comment them out temporarily to get Copilot++ back up and running.