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 go.mod changed from v0.0.0-20210201192233-b6486c6f1f2d to v0.0.0-20210417180633-a50937ef0888. Theoretically, an updated golang-github-go-ping-ping package, built from v0.0.0-20210417180633-a50937ef0888 or later, should resolve this bug. The go-ping commit responsible for fixing this bug is https://github.com/go-ping/ping/commit/38182647687148eb7c963dc57dc62456b12aa0ae, which was committed a little while after the currently packaged 0.0~git20210312.d90f377-1 version.
