Maximilian Haupt

Just had a look at node's http-parser and they do support even more methods. What do you think about adding all of them? https://github.com/nodejs/http-parser/blob/feae95a3a69f111bc1897b9048d9acbc290992f9/http_parser.h#L93-L134

Many tests are failing still. Working on it. ``` 1>------ Build started: Project: RUN_TESTS, Configuration: Debug x64 ------ 1>setlocal 1>C:\Users\max\opt\cmake-3.8.2-win64-x64\bin\ctest.exe --force-new-ctest-process -C Debug 1>if %errorlevel% neq 0 goto :cmEnd 1>:cmEnd...

The Ragel parser seems to be the problem. When using the stream parser, only 3 tests fail: For `Test_Server_body` i get this error: ``` unknown location(0): fatal error: in "body_too_big":...

And for completeness, list of dynamically linked DLLs according to `depends`: 

I am using cert-manager in an auto-scaled Kubernetes cluster in Google Cloud. The cluster is not able to scale down underutilised nodes, because the came solver pods are not backed...

See #38249 for an alternative implementation.

@erwinmombay can you please add someone else as a reviewer instead?

Hi @jarble we have a hard-coded retry count here: https://github.com/loophole/cli/blob/06767ef30bebf6095f1d93f6552d4727cc7ce241/internal/app/loophole/loophole.go#L102-L120 We could either always make it retry forever, or make the retry configurable via cli argument. @Morishiri what would you...

Hi @Tensha sorry that loophole desktop client is not working for you at the moment. Which version of chrome is installed exactly? We will try to reproduce and fix it....

Below you can find the output of the debug log. I will try other authentication types (password and different key types) and let you know. ``` SSH server successfully started...