Ellen Emilia Anna Zscheile

[log file](https://ytrizja.de/misc/27c2e4653698d69d614591999def1b10f5aa12cad4bd62002a422f65f18d1832.log)

relevant snip: ``` AWS: [DEBUG] 2021-12-03 07:49:46.278 CURL [140537079085696] (Text) Connected to 192.168.16.1 (192.168.16.1) port 9000 (#0) AWS: [DEBUG] 2021-12-03 07:49:46.278 CURL [140537079085696] (HeaderOut) PUT /nix-cache/nar/1i6530iyipd83rad3lg0v3hsr871ln6nmzxmvpvvdm3c7yndfscv.nar.xz HTTP/1.1 Host: 192.168.16.1:9000 Accept:...

@jmklix you should afaik remove the `feature-request` tag, because this is not a feature request, I don't need HTTP/2 support, I just want working HTTP/1.1 authentication, which somehow is skipped...

I tested using: ```perl use strict; use warnings; use HTTP::Server::PSGI; my $server = HTTP::Server::PSGI->new( host => '::1', # host => '127.0.0.1', # alternatively port => 8080, timeout => 1, ipv6...

It might be useful to invoke the `hydra-notify` service in strace, to look where it goes wrong (I have no Hydra running here, and setting one up just to test...

Should this perhaps also include `::` (IPv6)?

It feels like removing stuff from `setup.cfg` instead of from `setup.py` (which could just parse the `setup.cfg` and get that information from there) is a mistake, simply because it removes...

It might be a good idea to bless an outputs which starts to become common in flake projects; like `lib`, `nixosModule` outputs. I think the reasonable thing to do about...

I think "on different unique fd in each of the pollers / threads also won't work?" should usually work, but might not work on some OS supported by `polling`.

@uristdwarf done.