I have also seen this. I don't know the exact reasons, but you can 'fix' it with this setting in development.rb: config.cache_classes = true
This also means however that you will have to restart the server way more often to see your changes.. On Aug 29, 9:18 pm, Dave <hunkyb...@gmail.com> wrote: > Hi, > > RVM REE > RadiantCMS 1.0 rc2 > > using Pow.cx to take care of the development site... go to view the > homepage... reloader problems... > > ThreadError: thread 0x1001d6270 tried to join itself > ~/.rvm/gems/ree-1.8.7-2011.03/gems/radiant-1.0.0.rc2/vendor/rails/ > actionpack/lib/action_controller/reloader.rb:31:in `lock' > ~/.rvm/gems/ree-1.8.7-2011.03/gems/radiant-1.0.0.rc2/vendor/rails/ > actionpack/lib/action_controller/reloader.rb:31:in `run' > ~/.rvm/gems/ree-1.8.7-2011.03/gems/radiant-1.0.0.rc2/vendor/rails/ > actionpack/lib/action_controller/dispatcher.rb:108:in `call' > ~/Library/Application Support/Pow/Versions/0.3.1/node_modules/nack/lib/ > nack/server.rb:146:in `handle' > ~/Library/Application Support/Pow/Versions/0.3.1/node_modules/nack/lib/ > nack/server.rb:99:in `start' > Show 6 more lines > > Anyone have any tips on how to develop with Pow and not have this > issue with actionpack? > > Thanks
