Rutger Storm

@BenFradet You ever got this one done? All integration tests are still failing it seems.

We have had these problems too. We have been in contact with Azure Support and they are saying the following: " **Conclusion**: The 503s were detected ONLY on Azure Front...

This issue has also been raised here: https://github.com/OmniSharp/omnisharp-vscode/issues/1059 in the past. To be honest it's quite understandable that Microsoft wants to protect the value of Visual Studio and their other...

@tetious TBH the demands you are making are kind of not making sense. The key thing in this incident is that Microsoft made it's own debugger implementation based on a...

@tetious except the debugger that they used wasn't made by the team which develops the OpenSource platform. So you can totally see the people who made the debugger implementation as...

@tetious They have commented on this issue in https://github.com/OmniSharp/omnisharp-vscode/issues/1059 . But as you can see the people commenting on that thread say that it is above their pay grade and...

@salaros That's a little bit shortsighted tbh. It's an undeniable fact that Microsoft gives a lot back to the community and actively participate in the community. It's ethically incorrect to...

@scherenhaenden "We love Open Source" doesn't mean they have to open source everything. And I think https://opensource.microsoft.com/ is indication enough of the "We love Open Source" statement. It works on...

@justinyoo I understand you linking the standard but do you know of a way to mark it nullable then which is valid according to the spec? I see that other...

I got some messages that we got hit again. We are not entirely sure if it was the same cause as this issue but we had "Service unavailable" a couple...