khimaros

I believe what's described here is one of the primary motivations for "instance-hopping" (or, alternatively, for setting up a custom instance). I often find myself wishing that I could filter...


was this ever mainelined?

@conundrumer is this pull request of interest to you?

on debian buster, where libportaudio0=18.1 is available, i'm seeing a different issue which seems related to backtrace-rs: ``` = note: /usr/bin/ld: /home/user/audioscope/target/release/deps/libbacktrace-79a7a90134906214.rlib(backtrace-79a7a90134906214.backtrace.buo4lypt-cgu.2.rcgu.o): in function `backtrace::symbolize::libbacktrace::resolve': backtrace.buo4lypt-cgu.2:(.text._ZN9backtrace9symbolize12libbacktrace7resolve17hb68923a7654d7c7aE+0x90): undefined reference to `backtrace_pcinfo'...

https://github.com/conundrumer/audioscope/pull/19 fixes the build on debian/raspbian buster and possibly others by pulling in the latest version of backtrace-rs and some other transitive deps. the jack linker errors seem to be...

i believe this can now be closed since #19 was merged

same problem with `1.49.0-nightly (31ee872db 2020-10-28)` continuous integration started failing starting with [test suite #36](https://github.com/avr-rust/template-bin/runs/1064704696?check_suite_focus=true). last successful was [test suite #35](https://github.com/avr-rust/template-bin/runs/1059427629?check_suite_focus=true) which was built using `nightly-2020-08-28`. the following workaround helped:...

see also: https://github.com/avr-rust/blink/issues/25 and https://github.com/rust-lang/rust/issues/76930

thank you for considering this! would you accept a PR adding this as a preference? if so, how would you prefer to see the preference exposed in the UI?