Sebastian Krysmanski

How does one vote for a bug report? Thumbs up? Thumbs down? ;) In any case, I also ran into this issue: fresh Vagrant 2.2.16 install, first command from the...

So I did some more digging. Even simple commands like `vagrant --help` produce this error. I also tried to use cmd (instead of Windows Terminal) but I'm getting the same...

Just a quick thought (and sorry if this has been discussed before): Instead of creating a check, couldn't you use the same mechanism that https://github.com/actions/upload-artifact uses (under the assumption that...

@jonsequitur > We weren't satisfied with the security of the design. Could elaborate a little bit on what you mean by this exactly? :)

I‘ve recently heard that Swarm is simply dead (no work is being done to it anymore). It was no official statement but one from someone who does containers for a...

I also ran into this but with `CamelCaseNamingConvention` (I didn't know it was different than PascalCase). I have a class like this: ```c# namespace WishListApp.DataModels; public sealed class WishListAppSettings {...

The schema is (apparently) located here:

Just quick note: With the rename from `config.yaml` to `hugo.yaml` vscode now pulls a (partially broken) JSON schema out of its head (which it also applies to yaml files).

See also #10984.

I got stomped today by this issue and I'm still seeing it in version 1.17.11461.0 (which makes me wonder why this would have worked in 1.16). I'm using something slightly...