acud

@rcholic this would probably work but in my experience not considered a best practice. http files are usually served from within one directory, security reasons being one of the considerations...

In the case of the windows panic the test was constructed like so: ```go srv, _ := mockdns.NewServer(map[string]mockdns.Zone{ "ipv4.com.": { A: []string{"192.168.1.34"}, }, "ipv4and6.com.": { A: []string{"192.168.1.34"}, AAAA: []string{"2001:db8::8a2e:370:1111"}, },...

Nice catch. Added the error check but did not manage to get around to actually checking it, but we just got this on the windows CI, right now it seems...

this is a bit of a strange way to manage dependencies. is there a particular reason for the aversion towards using semver and tagging a release? there has already been...

On bee side - not sure, since k8s is polling these endpoints too, it means that they might need to be implemented to support both ws and normal json responses....

Hello Dearies, Swarmer here to support

No clue whatsoever @marten-seemann. Would you have an idea on how to actually check that? would I have to check the bind addresses for libp2p then try to telnet from...

> Add retry after sync failure. what does this mean?

related to #2026

tagging this as `wontfix` as i cannot reproduce this locally