-
Notifications
You must be signed in to change notification settings - Fork 143
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
bin/dev crashes on new app #166
Comments
I've been hitting a similar issue:
The I'm running inside a docker container (with tty: true set) and have removed the ruby debug env var, but it still crashes. I'm still using webpack, and note that it seems to take 30-40 seconds to build the assets every time I start up (which isn't ideal) - I wonder if that long build time causes something to be unresponsive and causes foreman to be marked for death? I have noted that if "left alone" after starting up, the process seems to no longer crash after 1-2 requests, whereas queueing up 2-3 requests whilst webpack is compiling seems to correlate with the server serving up one page, and then dying. Nothing crashes when I run all my Procfile tasks in separate containers |
This is happening to me too... macOS Sonoma 14.1, Ruby 3.2.2 and Rails 7.1.1. No docker. Like the OP, it seems to be caused by Reproducible on any new app that uses Foreman. For example:
|
Figured it out @diegomichel. It's because we have long computer usernames. Ruby debug generates a socket name that is too long. Yours is 24 characters (diegomichelrubioramirez) and mine is 23 (matthewlindfieldseager). Suggest you close this issue and plus one the issue there. @phantomwhale, your issue looks different. Ours was crashing at Rails startup, yours is crashing during the app lifecycle. |
The flag causes errors on socket name length when the current username is over a certain number of characters: rails/jsbundling-rails#166
On Mac when using the bin/dev script the web server crashes, here are the logs. Please excuse me if this is not the correct gem to report this :).
Looks like env command on
Procfile.dev
might be causing the issue, probably an env var?changing
env RUBY_DEBUG_OPEN=true bin/rails server
to justenv bin/rails server
fixes the issue 🤔 .The text was updated successfully, but these errors were encountered: