Steven Hartland

Any update on getting this merged?

Thanks @joeycumines @danmrichards @lwaddicor worth considering switching over to this more maintained fork?

Great little tool, showing my support by submitting this enhancement 👍

The workaround `args: "--out-${NO_FUTURE}format colored-line-number"` fails when run on windows: ``` Running [D:\a\_temp\99ad0a77-8d39-4bd4-a4a4-65b1acdcc359\golangci-lint-1.46.2-windows-amd64\golangci-lint run --out-format=github-actions --out-${NO_FUTURE}format colored-line-number] in [] ... level=error msg="Can't get config for command line: can't parse args:...

The issue is that the `middleware.OapiRequestValidator` validates the path exists in the spec so when other routes are added it triggers `no matching operation was found`. The workaround for `chi`...

Thanks @MikeRalphson the option is now there but the behaviour seems odd. - When you select it says attached for a few seconds in a small popup but doesn't show...

Installing python for windows solved the issue, but still odd that its not mentioned as a requirement especially as it seems to be able to run python code otherwise it...

Only standard signals are defined under windows, the more custom ones like SIGUSR1 etc simply don't exist so no this wont work under windows.

Not sure I follow you there @fvbock signals don't really exist on windows. If you wanted to be portable I would suggest you remove the signal handling from the core...

Yer the problem is more that there is no good replacement on windows so it would always need to be implementation specific. In my head removing signal handling totally and...