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
`synchronize': can't be called from trap context (ThreadError) #46785
Comments
This issue has been automatically marked as stale because it has not been commented on for at least three months. |
I'm seeing the same error using Rails/Puma/ViewComponent/Listen:
@aaronjensen Did you happen to find a fix/workaround? |
@ksweetie I tested w/ |
This issue has been automatically closed because there has been no follow-up response from the original author. We currently don't have enough information in order to take action. Please reach out if you have any additional information that will help us move this issue forward. |
Steps to reproduce
I reported this to guard/listen#565 as well, in case the fix needs to be there.
Use:
And puma as your web server. The warning happens randomly, but when it does you will see:
It appears to be
action_view/cache_expiry
that is being finalized (the below is thecaller
ofinitialize
that I store to print again in the finalizer.Expected behavior
No warning, it seems like stopping listen in a finalizer is error prone because those may run in traps.
Actual behavior
The warning
System configuration
Rails version: 7.0.4
Ruby version: 3.1.2
The text was updated successfully, but these errors were encountered: