Quentin de Metz

It's my first time using it and I've never used a previous version of Chef…

Thanks! Here is the stack trace: ``` INFO: Using configuration from /home/qdm/workspace/web/chef-repo/.chef/knife.rb Inspecting cookbooks -------------------------------------------------------------------------------- DEBUG: Chef::HTTP calling Chef::HTTP::JSONInput#handle_request DEBUG: Chef::HTTP calling Chef::HTTP::JSONToModelOutput#handle_request DEBUG: Chef::HTTP calling Chef::HTTP::CookieManager#handle_request DEBUG: Chef::HTTP calling...

Yep, doesn't crash! Hurray! Thanks a million!

Here is the verbose output: ``` INFO: Using configuration from /home/qdm/workspace/web/chef-repo/.chef/knife.rb Inspecting cookbooks -------------------------------------------------------------------------------- DEBUG: Chef::HTTP calling Chef::HTTP::JSONInput#handle_request DEBUG: Chef::HTTP calling Chef::HTTP::JSONToModelOutput#handle_request DEBUG: Chef::HTTP calling Chef::HTTP::CookieManager#handle_request DEBUG: Chef::HTTP calling Chef::HTTP::Decompressor#handle_request...

The next cookbook is bash-cookbook which I use to write my bashrc, bash_profile, etc. The differences I am getting are wrong however, because I'm getting the following output: ``` Inspecting...

Good find !

``` $ ls roles/ README.md app.json base.json ftp.json worker.json ```

(oops)

This issue occurs when I'm running knife-inspect from a subdirectory of my chef-repo.

Looks like the relevant issue has not been fixed in chokidar (https://github.com/paulmillr/chokidar/issues/395).