Tim Rühsen

If you want to use `[]byte` as key, you can't do it directly because it does not satisfy the built-in `comparable` constraint. You can either convert keys to `string`, which...

@mx-psi Thank you for the pointer. I just left a comment (https://github.com/open-telemetry/semantic-conventions/pull/99#discussion_r1683104887). My use case would be profiling, where we use the number of logical CPUs as part of the...

Hey @trask, thanks for the links, just my point of view... > I'm not sure if cpu cores can be a resource attribute today since it is potentially mutable (open-telemetry/opentelemetry-specification#2384...

@mx-psi What is the current state? Any advice on how to go on?

That is possibly a rate limiter on the server. Please check if --wait, --random-wait, --limit-rate helps here.

Use --progress=none to see the textual output including response codes. I'll take a look into why -R keeps the files in a few days.

> When fetching something with wget2 that is only reachable via IPv4, by default wget tries IPv6 and then fails. You are using `-t1`, so wget2 would give up after...

> The -t1 does not really matter, if I leave that one out, wget2 just tries IPv6 over and over: Oh, this sounds like a regression. Thanks for insisting, I'll...

From my first tests; the the fallback to the second (third etc) IP address doesn't happen if the failure isn't detected immediately by the `connect()` function. It looks like fixing...

To reproduce (requires commit ff881ed20182950accf77cf70bcaf51ec75d1a87 or later): ``` wget2 -d --dns-cache-preload=dns.cache https://www.spinics.net ``` with `dns.cache`: ``` f604:9a00:2010:a03b:4::114 www.spinics.net 207.244.127.203 www.spinics.net ``` (The ipv6 address should be invalid/unroutable on your system)