I didn’t use bundler in my configurations though I found few configurations for that while resolving my errors. In puma.rb, I updated the env variables as PUMA_WORKERS=0 and RAILS_MAX_THREADS=1 and it worked for me as well! Since I am working locally so multithreading doesn’t matter to me. So, somewhere deep down in a GitHub issue, I found a solution in bradleygolden’s comment. * Version 3.12.2 (ruby 2.5.3-p105), codename: Llamas in Pajamas * Min threads: 1, max threads: 16 * Environment: development * Process workers: 4 * Preloading application * Listening on tcp://localhost:3000 Use Ctrl-C to stop ! Terminating timed out worker: 51753 ! Terminating timed out worker: 51754 ! Terminating timed out worker: 51755 ! Terminating timed out worker: 51756 Upon executing rdebug-ide - host 0.0.0.0 - port 1234 - dispatcher-port 1234 - bin/rails s and attaching listener to it, the server tried to start but workers were terminating like: Rails 6.0.2.1 application starting in development => Run `rails server -help` for more startup options warning: constant ::Data is deprecated Puma starting in cluster mode. There was one more issue I faced while starting the server in debug mode. Next, the server was already running in debug mode, so run the script just created and finally get it worked!ģ. I ran the following shell command to generate your env: $ printf "\n\"env\": Janniks answer on StackOverflow suggested my environment variables ( env) are most likely not set. I was getting the following error in the debug console: Debugger terminal error: Process failed: spawn rdebug-ide ENOENT Everything was running great with the newly created Rails project but not with the existing project I am assigned to in my task. What? Got some error? Refer to some I also got and workarounds I found… Troubleshootingġ.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |