Greg Karekinian

It looks like having `Warbler::Task.new` in your Rakefile only creates problems, I also get a "stack level too deep" error when running `warble executable war` if it's in there.

I only have one `postgresql_access` resource with the name `replication`, however I created a simplified test recipe and I can't reproduce the issue. Now I'm thinking the bug is related...

@damacus I have created a repo that reproduces this in Vagrant. The issue does not happen when the `postgresql_access` resource is used directly in a recipe, I'm updating the issue...

That's a good idea. It should probably only be enabled in development mode

I forgot that in dev mode the root contains links to the demos: 

Hi, I'm not sure yet why that variable is set to`nil` but I found the bug. I'm writing a test for it and I'll fix it and release a new...

@blueharford Sorry I took so long to get back to you. Can you try the fix_cookbook_crash branch I've created? It should at least give more information about which cookbook made...

Hi, thanks for reporting this issue! It looks like it's the same error as #38. I need to work on it some more to find in which cases it can...

@quentindemetz Can you try the fix_cookbook_crash branch I've created? It should at least give more information about which cookbook made it crash. The easiest way is to change your Gemfile...

Thanks a lot, that's going to help me really fix that bug