Skip to content
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

ThreadError resque:no_fork resque:work New Level: Error Unhandled can't be called from trap context (ThreadError) #2495

Open
iuliabirleanu opened this issue Dec 13, 2024 · 2 comments

Comments

@iuliabirleanu
Copy link

iuliabirleanu commented Dec 13, 2024

Issue Description

When trying to upgrade our sentry-ruby version from 5.21 to the latest 5.22, I noticed the following error:

ThreadError resque:no_fork resque:work
Unhandled
can't be called from trap context (ThreadError)

The trace indicates the error is coming from sentry-ruby/lib/sentry-ruby.rb at line 310 from inside get_main_hub.
get_main_hub was indeed updated in the last release, but I can not say why is generating the error above.

Reproduction Steps

I don't know what triggers it.

Expected Behavior

The error mentioned above should not be present.

Actual Behavior

The error mentioned above is present.

Ruby Version

3.2.6

SDK Version

5.21 - 5.22

Integration and Its Version

Rails 7.0.8.5

Sentry Config

Exceptions.configure do |config|
  config.sentry.with(
    enabled: ENV.fetch('SENTRY_ENABLED', 'false') == 'true',
    dsn:  ENV.fetch('SENTRY_DSN', nil)
  )
  config.generate_fingerprint = false
end
@sl0thentr0py
Copy link
Member

@solnic this is because of the new mutex, not sure why it happens.

@solnic
Copy link
Collaborator

solnic commented Dec 19, 2024

Could you share the stacktrace too?

@getsantry getsantry bot moved this to Waiting for: Community in GitHub Issues with 👀 3 Dec 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Waiting for: Community
Development

No branches or pull requests

3 participants