-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
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
Panic initializing the logger from ruby gem #147
Comments
I also ran it with
|
With
The rest is the same backtrace as before, but with addresses added. |
Looks like the code is calling: pretty_env_logger::init_timed(); I checked the source of that, and internally it's calling the It might be better to call You might also look into updating pretty_env_logger. The current version is 0.5.0. |
I checked the new version that came out on April 15, and it still has the same issue. |
Describe the bug you encountered:
Trying to configure Pyroscope from Ruby, and I got a panic on the initialize_logger call.
What did you expect to happen instead?
It should have initialized.
How did you install
pyroscope-rs
?Then configured it with (just showing the code that ran before the crash):
Note that no other gems were loaded, aside from bundler itself, because I was wanting to profile startup times. I also tried loading it after all the other gems loaded, and got the same result.
pyroscope-rs version and environment
Ruby 3.1.2
macOS Ventura 13.6.5, Intel Core i9
pyroscope gem 0.5.10 (pyroscope-0.5.10-x86_64-darwin.gem)
The text was updated successfully, but these errors were encountered: