Debug console missing when session sending output while not fully initialised

[roblourens]

Debug console.log('hi')

• Get console output
• Click Clear Console
• Nothing happens

Sometimes, I start debugging and get no console output at all

[thpeder]

I have a similar experience with the insider c72cb12.
After I change the field name and tries to debug again then it doesn't update the messages in the output panel (see the timestamps for each line) and only when I click clear then it shows some of the messages:

[isidorn]

@roblourens oups this somehow feel through my fingers, sorry about that. Can you still reproduce with the latest insiders? Becuase I can not following your steps
@thpeder that issue I probably introduced yesterday. Can you try to reproduce with running a simple node program
console.log('hello')
Or any reproducable steps would be really helpful for me. Thanks

[roblourens]

I don't think I've seen it lately. I can't repro right now.

[isidorn]

@roblourens got it. So your issue is probably fixed
Let's wait for @thpeder for a potential reproducable sample

[thpeder]

@isidorn it might take a bit of time to get a solid repro, but I can give you the trace of what was sent from the language server, would that help?

[isidorn]

@thpeder I would prefer repro steps, any time in the next 30 days would be great.
We will also see if more users hit this.
Thanks a lot

[thpeder]

@isidorn It seems like the logic for when it shows the output messages has changed.
We are sending messages to the debug output panel before replying to the Launch request and if the response to the Launch request is not a success then it doesn't show them.
I have changed the Mock-Debug-Adapter project to reproduce the problem, see here thpeder/vscode-mock-debug.

[isidorn]

@thpeder thanks for the nice repro steps, the fix should be ini tomorrows vscode insiders.
Please try it out and let us know if this fixes the issue for you.

[StanislawStempin]

Could you please include this fix in the recovery build 1.29.2? We have many reports from developers using our AL Language extension that they are hitting this issue.

[isidorn]

@StanislawStempin hi, currently the recvoery build 1.29.2 is not planned.
However if we decide to do this we can include this fix.

My suggestion is to either tell your developers to use vscode insiders
Or to do a recovery release of your extension which fixes this in the following way:
send messages to the output channel while a debug session is not fully initialised, reveal the output channel and hide it appropriatly

Kind regards