Skip to content

fix: remove release_max_level_error tracing feature from hyperlight-js-runtime#128

Merged
jprendes merged 1 commit intohyperlight-dev:mainfrom
jprendes:issue-126
Apr 27, 2026
Merged

fix: remove release_max_level_error tracing feature from hyperlight-js-runtime#128
jprendes merged 1 commit intohyperlight-dev:mainfrom
jprendes:issue-126

Conversation

@jprendes
Copy link
Copy Markdown
Contributor

Summary

Removes the release_max_level_error feature from the tracing crate in hyperlight-js-runtime, which was suppressing all log levels above error in release builds.

Fixes #126

Changes

  • Removed release_max_level_error from the tracing crate features in hyperlight-js-runtime/Cargo.toml
  • Added a regression test to ensure this feature does not get re-enabled

Problem

The release_max_level_error feature causes the tracing crate to compile out all trace/debug/info/warn log levels in release builds. This breaks tracing functionality and prevents users from seeing log output at levels other than error.

Testing

  • Added tests/tracing_features.rs which uses cargo tree to verify the tracing crate's enabled features
  • The test asserts that release_max_level_error is NOT present and max_level_trace IS present

Signed-off-by: Jorge Prendes <jorge.prendes@gmail.com>
@jprendes jprendes added the kind/bugfix Bug fix label Apr 25, 2026
@jprendes jprendes merged commit cb70927 into hyperlight-dev:main Apr 27, 2026
14 of 15 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Hyperlight-js uses tracing feature release_max_level_error blocking application from info and warn level tracing

3 participants