You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Hyperlight-js uses tracing feature release_max_level_error blocking application from info and warn level tracing #126
Applications using hyperlight will inherit these tracing features, which blocks emission of logs of lower level than error. Below is a screenshot of a release build running hyperlight-js.
See: src/hyperlight-js-runtime/Cargo.toml
tracing = { version = "0.1.44", default-features = false, features = ["log","attributes","max_level_trace","release_max_level_error"] }
@copilot,
Please remove the release_max_level_error feature from the hyperlight-js-runtime crate to fix this issue.
Please also write a test that uses cargo hyperlight tree -p hyperlight-js-runtime -f "{f}" -i tracing --depth 0 to assert that the release_max_level_error is not enabled (you should use the cargo-hyperlight library to write a rust test).
Activity
jprendes commentedon Apr 25, 2026
@copilot,
Please remove the
release_max_level_errorfeature from thehyperlight-js-runtimecrate to fix this issue.Please also write a test that uses
cargo hyperlight tree -p hyperlight-js-runtime -f "{f}" -i tracing --depth 0to assert that therelease_max_level_erroris not enabled (you should use thecargo-hyperlightlibrary to write a rust test).