-
Notifications
You must be signed in to change notification settings - Fork 97
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
hang on startup with 5.3.5+ and carrierwave #512
Comments
Sorry for the trouble there, and thanks for narrowing it down. Based on the context of that commit, I wonder if there are other things in your app that were using the hook ( If you post a Gemfile or otherwise dump things that are registered to that hook, we might be able to narrow it down farther/see what is executing before it wedges. Meanwhile we'll put an environment together with those specs. This is the first we have heard of this particular issue and it makes me very curious about what is going on. |
Nothing in our codebase is using after_initialize callers
What's interesting is that the Nonetheless, I think this was fruitful, because this pointed me to instrumenting the In this case, we're migrating to ActiveStorage anyway, so dropping Carrierwave seems like straightforward solution. Perhaps someone cleverer than I can figure out why carrierwave and scout_apm are fighting this way. |
Nicely done. Thank you again for taking the time. Updated the issue title to highlight the conflict while we take a look. |
After upgrading a simple Rails app from scout 5.3.3 to 5.4.0, puma now hangs on initialization.
strace
shows that it's spinning on a futex; the process also ignores SIGINT, which seems kind of rude (but does respond to SIGTERM). Everything works fine if starting arails console
or other interactive process; it's something unhappy between scout and puma.Downgrading to 5.3.3 fixes the problem; upgrading to 5.3.5 or 5.4.0 reproduces it.
Bisection points to 37c88b8 as the offending commit; everything works in 679670e but and hangs in 37c88b8.
Relevant specs
Ruby: 3.3.5
Rails: 7.2.1.2
The text was updated successfully, but these errors were encountered: