We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
-debug
EmbeddedFile
Hadley loaded a debug build and saw:
thread 'main' panicked at crates/harp/src/lib.rs:77:29: called `Result::unwrap()` on an `Err` value: can't open asset init.R Stack backtrace: 0: std::backtrace::Backtrace::create 1: anyhow::error::<impl anyhow::Error>::msg 2: anyhow::__private::format_err 3: harp::modules::with_asset 4: harp::modules::init_modules 5: harp::initialize 6: ark::interface::RMain::start 7: ark::start::start_kernel 8: ark::main 9: core::ops::function::FnOnce::call_once 10: std::sys::backtrace::__rust_begin_short_backtrace 11: std::rt::lang_start::{{closure}} 12: std::rt::lang_start_internal 13: std::rt::lang_start 14: _main
init.R is an embedded file, during debug embedded files are read from the file system, but he doesn't have that file!
init.R
debug
According to https://docs.rs/rust-embed/8.5.0/rust_embed/trait.RustEmbed.html#required-methods we can use the debug-embed feature to force it to load from the binary even in debug mode.
debug-embed
This currently means all of the -debug releases we generate are likely DOA
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hadley loaded a debug build and saw:
init.R
is an embedded file, duringdebug
embedded files are read from the file system, but he doesn't have that file!According to https://docs.rs/rust-embed/8.5.0/rust_embed/trait.RustEmbed.html#required-methods we can use the
debug-embed
feature to force it to load from the binary even in debug mode.This currently means all of the
-debug
releases we generate are likely DOAThe text was updated successfully, but these errors were encountered: