Closed wexgjduv closed 1 year ago
Seems that this is not the first time panic occurs, as the once
will keep panic as long as the initial once_fn is paniced. Could you find some previous panic messages that is not reported as "poisoned"?
Thanks @breezewish for your reply. I could find some panic messages like:
thread 'tokio-runtime-worker' panicked at 'called `Result::unwrap()` on an `Err` value: Other("Failed to parse patch version")', /usr/local/cargo/registry/src/github.com-1ecc6299db9ec823/procfs-0.9.1/src/lib.rs:303:34
But I'm not sure these panics are related.
Most of the time, 'Once instance has previously been poisoned' is the ONLY panic.
I think this is a duplicate of https://github.com/tikv/rust-prometheus/issues/414, which should be already fixed in latest release.
Closing this report, supposedly already fixed.
Hi, I'm using this library to export metrics in Pulsar Elasticsearch Sync, however, ProcessCollector occasionally causes tokio runtime worker panic. Below is the backtrace:
I'm using prometheus 0.12.
Thanks