It's not a specific answer to your problem, but it might solve it: I ran into a lot of issues which were fixed by switching to rc5 - I notice in your gemfile you're using rc3. I was getting a lot of hiccups like this when I was on rc4.
It's not a specific answer to your problem, but it might solve it: I ran into a lot of issues which were fixed by switching to rc5 - I notice in your gemfile you're using rc3. I was getting a lot of hiccups like this when I was on rc4. You don't need to add sprockets in your gemfile anymore once you do this either.
Also, you don't mention it but do you have gem 'jquery-rails' in your gemfile too?
I did have jquery-rails. Moving to rc5 made things better certainly. However, it still times out to fetch assets/application.
Js and assets/application. Css and actually kills the server with: . Gem/ruby/1.8/gems/tilt-1.3.2/lib/tilt/template.
Rb:38: BUG rb_gc_mark(): unknown data type 0x3a(0x105608c58) corrupted object ruby 1.8.7 (2009-06-12 patchlevel 174) universal-darwin10.0 Not sure if I need ruby 1.9.2 or something else? Also do I need to somehow precompile the manifest files or rails does that on startup? – Bashir E Aug 9 at 9:05 Rails compiles when the server starts up so you don't need to do that... As to upgrading to ruby 1.9.2 I don't think that's your problem but I always think it's best practise to future proof yourself by working with the latest versions.
If you're comfortable enough to be using Rails 3.1 then you should definitely be moving up to Ruby 1.9.2 ...also if you're thinking about using Heroku Cedar supports both Rails 3.1 and Ruby 1.9.2 - that's what I am using – Richard Jordan Aug 9 at 19:29.
As Richard pointed out, moving to rc5 helped: gem 'rails', '3.1.0. Rc5' but I was still getting "stack level too deep" issues which I finally figured out was due to my version of sprockets (beta.13) so I added a previous version the gem file: gem 'sprockets', '2.0.0.beta.12' and things are working fine :).
I was running into this problem as well and it took me a lot of tinkering to get it back to a working state. What I finally ended up doing that worked is: Adding the following line to application. Rb: Bundler.
Require *Rails. Groups(:assets) if defined?(Bundler) Changing up my Gemfile so that I had the following defined: group :assets do gem 'sass-rails', "~> 3.1.0. Rc" gem 'coffee-rails', "~> 3.1.0.
Rc" gem 'uglifier' end Bundle install, relaunch my server and voila, I have css and js again.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.