John Starks

Results 11 issues of John Starks

`oneshot::Receiver`'s `FusedFuture::is_terminated` implementation will return true if the associated `Sender` is dropped without sending anything. I don't think this is the right behavior--it makes it hard to use a oneshot...

A-channel

## Bug Report ### Version ``` ├── tracing v0.1.40 │ ├── tracing-attributes v0.1.27 (proc-macro) │ └── tracing-core v0.1.32 └── tracing-subscriber v0.3.18 ├── tracing-core v0.1.32 (*) └── tracing-log v0.2.0 └── tracing-core...

The Rust libs team quietly decided to start blocking `-Zunstable-options` in Rust 1.70 outside of nightly builds. Rust 1.70 is now in beta. https://github.com/rust-lang/rust/pull/109044 ``` $ cargo +beta test --...

0.3.30: `Lines::poll_next` propagates the error from reader before it restores the invariant that `buf` is empty. This results in panics on IO failures. ```rust use futures::AsyncRead; use futures::StreamExt; use futures::AsyncBufReadExt;...

bug
A-io

Considering this from `Builder`: ```rust pub fn spawn(self, future: F, schedule: S) -> (Runnable, Task) where F: FnOnce(&M) -> Fut, Fut: Future + Send + 'static, Fut::Output: Send + 'static,...

On Linux, [clone](https://docs.rs/libc/0.2.95/libc/fn.clone.html) takes a callback function pointer. The function pointer type is not marked `unsafe`, but there is basically no way to implement this callback with a safe function...

breakage-candidate
C-bug
E-easy

Rather than having a `bsdtar_name` freefloating function, this should probably be backed by a `ctx.reqv(install_bsdtar::Request)`, which return a `PathBuf` to the bsdtar executable. That way, we can evolve the underlying...

flowey

`bsdtar` can extract just about everything. Don't have separate entry paths and tools for zip vs. tar.bz2 vs. some other thing in the future. Also, ensure extraction verifies the target...

If the sidecar kernel is not already 2MB aligned, then the offset is miscomputed due to variable shadowing. Fix this. In the future, we should get rid of this 2MB...

For convenience, mesh cancel contexts are timed out via a global timeout thread. Find a better way to manage this, e.g.: * Pass a `pal_async` driver to `until_cancelled`. This isn't...

enhancement