Nikolay Edigaryev

> I beilieve we need to allow that if the delete by tag returns 400, it is a `UNSUPPORTED` error. It seems like a more appropriate solution would be to...

@jdolitsky would you mind giving this a look once more? Thanks!

The [`configOverride`](https://github.com/cirruslabs/cirrus-ci-web/blob/b510b7cf8a9e65a12467f04fe38949a65ca280dd/schema.gql#L837) GraphQL field overrides the whole YAML configuration, not just a part of it. The Starlark configuration is left untouched since the Starlark option was introduced relatively recently to...

Please read the TLS section of [Docker image](https://hub.docker.com/_/docker): since 18.09+, TLS connection is used by default and is available on port `2376` (not `2375`). To enforce the old behavior, pass...

> What about the MySQL repro though? Sorry, didn't noticed that part of your message. It seems that if you want to supply an empty password via `MYSQL_ROOT_PASSWORD=""`, you also...

> As for the Docker in Docker, the section that you referred to says to use `dockerd` as the entrypoint (which afaik translates to `command:` in Cirrus CI's container configuration)...

What do you think about adding support for [`1909` version](https://cloud.google.com/compute/docs/images/os-details#windows_server)? Or it makes little sense to offer anything other than the LTS one?

This will also allow to catch errors that are only returned in the JSON stream.

> I just tried v0.45.0-07fb74e, but it didn't clear the directory. I presume the cirrus agent needs to be bumped on the cirrus servers first? I'm sorry you've had to...

> No worries, thanks for working on this. I just re-tested and it looks like it prefers the directory name `/tmp/cirrus-build-557367079/` over `/tmp/cirrus-ci-build/` Thanks, this means it's working. These should...