Is there a reason this library depends on a fork of `go-metric`s? Would it be possible to contribute the 2 commits upstream? It would be nice to depend on the canonical go-metrics as the fork keeps falling behind.
Is there a reason this library depends on a fork of
go-metrics? Would it be possible to contribute the 2 commits upstream?It would be nice to depend on the canonical go-metrics as the fork keeps falling behind.