Olivier Dormond

Hi @giampaolo! The compilation error is fixed for me by applying the following patch: ```diff diff --git a/psutil/_psutil_osx.c b/psutil/_psutil_osx.c index 67a52aa9..2effa0a0 100644 --- a/psutil/_psutil_osx.c +++ b/psutil/_psutil_osx.c @@ -214,6 +214,7 @@...

> I have only tested it on Intel mac yet but will give it a shot tomorrow on M1. I finally managed to get my hands on an M1 and...

I forgot to mention that you can reliably reproduce the problem but without being able to sort out whether it's the check or get operation that block the worker from...

> Hello! So everything in this falls within the expected behaviour of Concourse, so I don't think this is a bug and is actually a feature request/enhancement. Why? > >...

I just stumbled on this issue with Concourse 7.8.1. In contradiction with what is documented the first value encountered from several `var_files` is used instead of the last one.

Hi Vito, Yes. The VM will be thrown away and a new one will take it's place which result in a new worker with a different id. Without the option...

> @odormond are we still using the signal or did we switch to `concourse retire-worker ` ? We still have `KillSignal=SIGUSR2` in our systemd unit file. So we're still using...

Apparently all that is missing is returning application/json as Content-Type instead of text/plain.

> Apparently all that is missing is returning application/json as Content-Type instead of text/plain. https://github.com/prometheus-community/PushProx/pull/121 fixes that.

I'm facing the same issue using v5.2.0 and digging it I found out an important point that I haven't seen mentioned in this ticket: the `etag` stored in the terraform...