Max Inden
Max Inden
> Is there standardized process collector available as a library? I would like to have as a minimum something similar to Go, Python: As the above conversation says, the `prometheus-client`...
> but that can be solved by adding `is_` getters. How are these different to a non-opaque struct with a `non_exhaustive`? Removing them would still be a breaking change, right?...
I don't think anyone from the libp2p core team will be able to tackle these any time soon. Contributions are more than welcome. I am happy to help.
Can you expand on the use-cases that you want to solve with the above proposed changes?
> In the docs it says V1Lazy only applies to the dialer. Since the rendezvous point never dials anyone, I don't think it is needed here? My bad. Yes you...
Thanks for the input. No opinion here, i.e. not opposed to merging a patch. Just want to be consistent with Prometheus and/or OpenMetrics.
Should we introduce this in the version after https://github.com/multiformats/rust-multiaddr/pull/78? The version that includes https://github.com/multiformats/rust-multiaddr/pull/78 only would then error on `/webrtc` instead of interpreting it as the browser-to-browser protocol. Might prevent...
Moving to draft in order to not include in `v0.18.0`.
Still interested to get this merged @thomaseizinger! Writing a tiny protocol right now where this would come in handy for testing.
> Hence, the only feature that is currently provided and will be removed is the "backpressure" on inbound streams. It isn't really backpressure because it only works if the stream...