David Pacheco

My mistake. I thought this package was tied to the Go runtime and so needed a new Go release to get the fix. (Sorry for my ignorance here...I'm a user...

I've run into the same error message, which appears to cause reedline_repl_rs to [panic](https://github.com/arturh85/reedline-repl-rs/blob/e79fca1a4730cf61e96fa54b4896839715ebc353/src/repl.rs#L524-L526). In my case, the system I'm running on is heavily loaded and struggling to keep up,...

The "module" and "function" that DTrace knows about were historically the native module (i.e., kernel module, shared library, or "a.out") and native function name where the probe itself is defined....

I saw this too: ``` thread 'rustc' panicked at 'called `Option::unwrap()` on a `None` value', compiler/rustc_metadata/src/rmeta/def_path_hash_map.rs:22:85 stack backtrace: 0: 0xfffffc7fecea15a4 - std::backtrace_rs::backtrace::libunwind::trace::ha20bdf7275ee7b0d at /rustc/d5c2e9c342b358556da91d61ed4133f6f50fc0c3/library/std/src/../../backtrace/src/backtrace/libunwind.rs:93:5 1: 0xfffffc7fecea15a4 - std::backtrace_rs::backtrace::trace_unsynchronized::h2e9cadc5a81fff50 at /rustc/d5c2e9c342b358556da91d61ed4133f6f50fc0c3/library/std/src/../../backtrace/src/backtrace/mod.rs:66:5...

I think there's a good chance that @jmpesp and I were seeing a combination of https://www.illumos.org/issues/15367 and https://www.illumos.org/issues/15367. There's a detailed analysis of how those illumos issues can result in...

Thanks @prattmic for taking a look. I'm glad it turned out to be worthwhile (i.e., sounds like a real issue here).

@dr2chase Thanks. I'll look into the question of illumos builders for those recent releases.

@dr2chase Thanks. So we do already have one, but you mentioned it's not running several recent releases. Is there some config that needs to be changed somewhere to cover those...

The issue here was that we didn't get any error at all from hyper. (Again, sorry if I'm just missing the interface we should be using to get it. I...

Unrelated, but I just wanted to add: thanks for all the work on hyper! We've been using it (via Dropshot) fairly heavily in many components for about three years now...