squizzling

The macOS output appears to be from a much earlier version (at least 6014f24b0a426ae81301dddd4572250213d6cd50, July 2019). My best guess is you're running through docker-compose which is configured for `letsencrypt/pebble:latest`, and...

Because this has the potential to add artificial delays in something like a CI environment, I am particularly concerned about the "default enabled" for the new feature. The worst case...

I like the idea of consolidating and deprecating. Having 2 things under the VA flag is a bit of a code smell. Since it's a new interface, I'll collapse it...

In theory this is ready, however I have two concerns: - There's an API change (passing `sleepTime` to `ca.New` and `va.New`), so it may trigger a major version bump. I...

Should not be merged until #351 is handled, as it will increase the polling and make failures more likely.

Thanks for the feedback, I wasn't aware the mouse wasn't working in some Linux configurations. Perhaps we should flip the default.

I have a couple of ideas on how to do this one, not entirely sure it'll work but I'll give it a crack. It would definitely be good to allow...

The plotters keep running, but things get messed up because the server isn't reading logs anymore. My plan is to redirect the logs to a file, instead of having the...

That's because the plotter is writing to the plotng-servers pipes. The change will be to have the plotter write to disk, and then plotng-server reads from disk. There won't be...

All the plotter knows is to write to its stdout (fd 1). When you run the plotter from the commandline with nothing else going on, the stdout will go to...