Bug#998231:

A git bisect seems to suggest that https://github.com/go-ping/ping/commit/30a8f08ad2a9d0b88ca9c1978114d253f63748c3 is the commit which resulted in the regression in go-ping. Sadly that made it into the package that shipped with bullseye. I can update the go-ping package to a newer version that

Bug#998231:

I tested some upstream tags, i.e. "go run ..." to build with the exact module versions specified by their go.mod: v0.3.1 - OK v0.4.0 - counters latch at 65536 v0.4.1 - counters latch at 65534 v0.4.2 - OK master (as of writing) - OK Between v0.4.1 and v0.4.2, the go-ping version specified by

Bug#998231:

Unable to reproduce with an earlier, in-house build of smokeping_prober 0.3.1 (prior to first debian upload): # HELP smokeping_response_duration_seconds A histogram of latencies for ping responses. # TYPE smokeping_response_duration_seconds histogram

Bug#998231:

Reproduced with prometheus-smokeping-prober 0.4.2-2, built with go-ping 0.0~git20210312.d90f377-1. # HELP smokeping_response_duration_seconds A histogram of latencies for ping responses. # TYPE smokeping_response_duration_seconds histogram

Bug#998231:

Hello Tim, I have just uploaded prometheus-smokeping-prober 0.4.2-1, however I have not marked this bug as solved, since the only difference between 0.4.1 and 0.4.2 is that the upstream developer bumped the go-ping build dependency git snapshot in go.mod to a slightly later version. As far as I