Open Vaccano opened 3 years ago
Thanks @Vaccano for logging this issue!
This InvalidOperationException: The 'InvokeCoreAsync' method cannot be called if the connection is not active
is an error we've seen in our telemetry but that we could hardly reproduce. Adding @lolodi for FYI, as he's looking at this bug.
One of our hypotheses is that it was related to very long connections (let's say staying connected using Bridge for more than an hour). @Vaccano Could you please confirm if it is the case for you? Or does it reproduce as well for small ones?
Regarding the banner you see/the fact that you cannot debug again right after, that's something we should improve indeed. @danegsta Could you please let us know if you have an idea or where these might come from? Do we handle errors differently when stopping the connection (shouldn't we swallow this error and just log it on our side)?
It reproduces with much shorter debugging times. I just had it happen with a less than 5 minute debugging session. The time it happened that had me log this issue was less than 10 minutes tops.
OK thanks, it's definitely good to know! @lolodi on our side is looking into it, and we might ask you for more information if required.
I'm also getting the same error and after it happens VS has to be restarted because its... not working right anymore... text is missing where hints should be - getting empty spaces in text editor... and most importantly, its getting unresponsive or freezes completely. I'm guessing that the next VS extension is being run on the same thread and once BTK throws the exception, the extensions run loop (guessing) is broken or something similar.
@Vaccano did you see such behavior as well? if not, are you using additional extension? I suspect that resharper is the one getting broken in my case. The reason is that it influences the text editor in such a way that can result in the unusable state I`m getting.
@Rob623 - I have not seen any such issues. I do use ReSharper, but it has not interacted with Bridge to Kubernetes in any way I can see. Nor have I seen any issues with with my text editing in Visual Studio.
As I said in my bug report, starting up debugging right after stopping does not work out well. I got issues where my Kubernetes application service is put in an unstable state. I got error messages complaining about replicas and I had to re-deploy the application to Kubernetes to work around it. But these symptoms are not as what you are reporting. (And this is easily avoided by waiting a minute or two before starting to debug again.)
Hmm I see. since the stack trace looks the same, Im guessing that the issues are related however, since the symptoms appear to be different, @daniv-msft should I open a separate issue for it? btw I forgot to mention that I
ve also seen the problem @Vaccano mentioned.
Anyway, if I find more info or better reproduction scenario I`ll update.
@Rob623 Thanks, I think it's fine to keep the same issue for now as even though the symptoms are slightly different, I believe they have the same root cause. @lolodi made good progress on a tentative fix for this, and we will work to integrate them in Visual Studio to get the changes to you.
@daniv-msft @lolodi I've seeing the same issues here as well. mindaro-vscode-2021-07-14T05-47-42.911Z.txt Very easy to reproduce, if I stop at a breakpoint, continue, and then stop debugging I get this issue. I have a busy cluster which has previously caused timeouts in your commands in the past if that helps you track down the issue.
@daniv-msft @lolodi is there any update on the issue?
@tigerquoll Thanks for following up! We're releasing our new version (including the fix from @lolodi) in VS Code this week. It's already available to 10% of the customers, and we will gradually increase this if we don't detect issues. Visual Studio will come right after, so likely in 1/1.5 weeks.
Describe the bug When I stop debugging, an error message appears saying that something went wrong. It does not seem to cause any issues.
To Reproduce
When I open the log file, this is what is in it:
Click to Expand Log File Details