Steven Fackler

That output looks like it may be from rustc's own jemalloc. Try running your binary directly.

It checks that the version of the configure script that autoconf produces matches what's checked in here: https://github.com/gnzlbg/jemallocator/tree/master/jemalloc-sys/configure. You should just need to update that file.

With respect to question 2, the standard library's policy is to never define non-static methods to smart pointer types.

We could add a `TimeoutBody` wrapper to http-body-util, though that wold require making tokio an optional dependency. I can update the PR tonight.

Here's a TimeoutBody implementation (untested): ```rust #[pin_project] pub struct TimeoutBody { #[pin] inner: B, #[pin] timer: Sleep, timeout: Duration, waiting: bool, } impl Body for TimeoutBody where B: Body, {...

@seanmonstar thoughts on this?

I've updated this to move from `poll_healthy` to a more general `poll_progress`, like what boats described for the `Stream` trait. In addition to the error reporting case I opened this...

That seems like a reasonable-enough name to me, though it might be a bit strange to have `poll_closed` return `Result`? That's why the original name in the PR was `poll_healthy`.

A default implementation that just returns `Poll::Ready(Ok(()))` is correct, and equivalent to the current state of the world. I don't think it would indicate closure, just drive any background IO...

In that sense, it is really pretty similar to Boats's poll_progress, just fallible. We could make it infallible and force the error to come out of poll_frame but that just...