You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@khoaquoine The purpose of the ruby-build project is to help compile and install a Ruby version. Any runtime errors that happen while running that Ruby version are likely caused by other factors outside our control. I don't know why your crash happens, but you could try to reproduce it with a smaller Ruby program than a full-blown Rails instance, by switching servers from Puma to something else, by using a different Ruby version, etc. Then, when you have more information, you could report this to the project most likely to be able to fix the root cause.
@khoaquoine The purpose of the ruby-build project is to help compile and install a Ruby version. Any runtime errors that happen while running that Ruby version are likely caused by other factors outside our control. I don't know why your crash happens, but you could try to reproduce it with a smaller Ruby program than a full-blown Rails instance, by switching servers from Puma to something else, by using a different Ruby version, etc. Then, when you have more information, you could report this to the project most likely to be able to fix the root cause.
@mislav@hsbt yup, sorry to create the issue in here. That was mistake
Steps to reproduce the behavior
I was able to install ruby on Apple M2 Ventura 13.5 and rails app init ok, but it crashed right after I access
http://localhost:3000
Ruby: 3.0.5
Rails: 6.1.7.3
Below is the system Crash Report
Expected vs. actual behavior
Rails app works normally
Logs
The text was updated successfully, but these errors were encountered: