Caddy version: v2.2.0 h1:sMUFqTbVIRlmA8NkFnNt9l7s0e+0gw+7GPIrhty905A=

I am trying to pass pem-encoded client certificate to proxied service via a X-SSL-Cert header, like so:

sub.example.com {
    reverse_proxy 127.0.0.1:8000 {
        header_up X-SSL-Cert {http.request.tls.client.certificate_pem}
    }

    tls {
        client_auth {
            mode require
        }
    }
}

The library has many constant definitions that are declared as NAME = 'val', e.g. https://github.com/aio-libs/aiohttp/blob/master/aiohttp/client.py#L161

We need to add Final type hint to let users know that these constants should be considered as immutable (this hint doesn't prevent the actual modification and fully backward compatible).

from typing_extensions import Final  # suppor

The docs do not give a format option for iso date with microseconds. Is this possible?

In our codebase, we push RequestContext and immediately run some code with try-with-resources.
For example:

try (SafeCloseable ignored = ctx.push()) {
    logger.trace(decorate(msg));
}

If RequestContext provides run(Runnable) or call(Callable) we can reduce boilerplate code and simplify it.

ctx.run(() -> logger.trace(decorate(msg));

This is inspired by g

From the dotty branch,

++3.0.0-M1 core/compile

For now, ignore:

• Errors mentioning parboiled2 (#3761)
• Errors mentiong CollectionCompat (#3945)
• Errors mentioning literal macros (#3760)

What progress can we make? If they're indecipherable, can we begin to categorize them and make more tickets?

This is tedious work that won't land a feature during the Open Source event,

Hi, when implementing http4k/http4k#435 I noticed the codebase does not have a linter set up - e.g. some files end with new lines and some don't.

I am not sure whether this is desired, I would be happy to participate if wanted.