Carlos Konstanski

I think there is something nondeterministic in the loading of puri files that makes the issue intermittent. The ASDF people also could not reproduce. Yet they recognized the problem regardless...

This solution would work fine and be much appreciated. For context: I work at a major telecom and we're standing up 75k new ipv6-only hosts in the next three years...

Thanks for adding this. I'm still waiting for it to land in quicklisp. Once it does, I'll let you know how it goes.

I'm not running your code to actually see what the debugger says. But I can see things that jump out: - in `test-g': it's a macro. You need two backquotes...

I turned off HTTP/2.0 and still have the issue. A slightly different packet trace: POST /job/manage-pubkeys/build HTTP/1.1 MIME-Version: 1.0 Extension: Security/Digest Security/SSL Host: openbook-jenkins-master.mon.vzwops.com Accept-encoding: gzip Accept-charset: utf-8;q=1, gb2312;q=0.5, iso-8859-1;q=0.5,...

FWIW I disabled CSRF in my jenkins. It would give a similar (identical?) error if enabled. That potential issue is eliminated. I'm on version 2.207.1.

Now I get "400 nothing is submitted". ``` POST /job/ob-ctl-restart-unstable/build HTTP/1.1 MIME-Version: 1.0 Extension: Security/Digest Security/SSL Host: openbook-jenkins-master.mon.vzwops.com Accept-encoding: gzip Accept-charset: utf-8;q=1, gb2312;q=0.5, iso-8859-1;q=0.5, big5;q=0.5, iso-2022-jp;q=0.5, shift_jis;q=0.5, euc-tw;q=0.5, euc-jp;q=0.5, euc-jis-2004;q=0.5,...

You know what, you are right. This particular job does require a parameter. I wasn't thinking of it because it is an "optional" parameter in that I usually leave it...