onalante-msft

In that case, would it be acceptable to refer to `futures_util` for the crate links but keep `futures` in the doctests? This would obviate the need for the internal feature...

I understand the issue now, sorry about the confusion. I cannot get the reference to `futures_util::stream::select` at `kube-runtime/src/controller/mod.rs:239` to resolve, now that I can see the problem...

I believe the root cause for this is https://github.com/rust-lang/rust/issues/87048. When trying to resolve the link for `futures_util::stream::select`, the (original) function `futures_util::stream::select::select` hits [this error condition](https://github.com/rust-lang/rust/blob/master/src/librustdoc/html/format.rs#L581). This is because [`!cache.access_levels.is_public(did)`](https://github.com/rust-lang/rust/blob/master/src/librustdoc/html/format.rs#L577) (incorrectly...

One possible solution for the time being is to have use `--document-private-items` in the `cargo doc` invocation. That fixes the resolution issues for me, though it has the undesirable side...

I have been busy for the past few months, my apologies. I am going to continue this PR on https://github.com/onalante/tarpaulin/tree/ptrace after resolving the change conflicts.

Sorry about not following up on this. I am going to close this PR since A. chrono fixed its regression, and B. the upstream reporter modules are not a significant...