Hassan is right. I doubt the problem is with your Gemfile.lock so I suggest starting elsewhere and leaving it alone.
The best thing would be to stash your changes using git and going back to a working version of the application. Go back to the last version that worked and see what's different. Alternatively you can keep your current changes and just figure out what is happening with `place'. Search your files and make sure that everything is fine around that variable. It's clear the problem is with that so make sure that every instance of that variable is working and that should fix the problem that appears with the imports as well. On Monday, July 14, 2014 10:26:14 AM UTC-6, Hassan Schroeder wrote: > > On Mon, Jul 14, 2014 at 9:06 AM, Rasool SB <raso...@gmail.com > <javascript:>> wrote: > > > When ever we accidentally shutdown, Rails or Ruby files( temporary > > files) like "/tmp/pids/server.pid " and or "Gemfile.lock" caches logs to > > interact with some methods, classes etc., due to sudden close of the > > application when we try to run "rails s" it checks your gemfile.lock to > load > > the gems in to your environment, so the Gemfile.lock can't give right > > information due to sudden close. > > WAT?? If a Gemfile.lock was changed at runtime, it would show up in > a `git status` after every invocation of the server. So -- no. > > > By deleting the Gemfile.lock wont harm anything (it's kind of temp > file) > > by running "bundle install" you will get the "Gemfile.lock" file > > automatically when the bundle install finishes. > > It's in no way a "kind of temp file". > > Yes, you'll get a new Gemfile.lock running `bundle install`, but it won't > necessarily match the previous one unless you have explicit versions > set for each gem in the Gemfile. > > Deleting Gemfile.lock and re-bundling is a great way to muddy the > water when your app is already broken. Why would you want that? > > -- > Hassan Schroeder ------------------------ hassan.s...@gmail.com > <javascript:> > http://about.me/hassanschroeder > twitter: @hassan > -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscr...@googlegroups.com. To post to this group, send email to rubyonrails-talk@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/da6f02de-2eba-443d-a0a3-5812c7098d3a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
