This project is archived and is in readonly mode.
"route set not finalized" after a startup problem
-
David Trasbo- Assigned user set to Ryan Bigg
You'll have to elaborate on how to duplicate this issue. Meanwhile this ticket can be marked as incomplete.
-
Ryan Bigg- State changed from new to incomplete
-
Off TopicI am not able to redo the same bug because I don't have anymore the same environment.
I had a simple rails3 application using PG connection. My postgresql server was down, I started the rails app (scripts/rails server) and the I had a "route set not finalized". I was unable to using until stopping the rails app, starting postgresql server and restarting the rails app.
I won't be able to give more "details" or info. If that's not enough to understand about the bug, you can kill this ticket.
-
Ryan Bigg
So from what I can tell, this bug may be reproducable by stopping a postgresql server that Rails will connect to , starting the Rails application and then trying to access the database through it.
-
Santiago Pastorino
- State changed from incomplete to open
This issue has been automatically marked as stale because it has not been commented on for at least three months.
The resources of the Rails core team are limited, and so we are asking for your help. If you can still reproduce this error on the 3-0-stable branch or on master, please reply with all of the information you have about it and add "[state:open]" to your comment. This will reopen the ticket for review. Likewise, if you feel that this is a very important feature for Rails to include, please reply with your explanation so we can consider it.
Thank you for all your contributions, and we hope you will understand this step to focus our efforts where they are most helpful.
-
Santiago Pastorino
- State changed from open to stale
-