Page 1 of 1

How to find which rule causes errors?

PostPosted: Sat Jun 20, 2015 3:16 pm
by hepabolu
I've recently started from a clean Yosemite install on a new computer and moved my Hazel config files over from my old computer. Debug logging is on, and this is what I see constantly in the Hazel.log file:

Code: Select all
2015-06-20 21:00:06.914 hazelworker[1399] DEBUG: Program is licensed.
2015-06-20 21:00:06.965 hazelworker[1400] DEBUG: Program is licensed.
2015-06-20 21:00:06.986 hazelworker[1400] DEBUG: Unexpected type for Mail download URL: (null)
2015-06-20 21:00:07.006 hazelworker[1400] DEBUG: Error reading file /Users/helma/Library/Application Support/Firefox/prefs.js: Error Domain=NSCocoaErrorDomain Code=260 "The file “prefs.js” couldn’t be opened because there is no such file." UserInfo=0x7ff00ca2e040 {NSFilePath=/Users/helma/Library/Application Support/Firefox/prefs.js, NSUnderlyingError=0x7ff00ca2d8e0 "The operation couldn’t be completed. No such file or directory"}
2015-06-20 21:00:07.036 hazelworker[1400] DEBUG: Could not find entry for default_directory in Chrome preference file.


I can understand that it has something to do with FireFox and Chrome, but I can't find any rules using or depending on FireFox and Chrome.

What is causing this and how can I find these rules?

Re: How to find which rule causes errors?

PostPosted: Mon Jun 22, 2015 11:32 am
by Mr_Noodle
Those are unrelated to your rules. Hazel checks settings used by different browsers to figure out certain behaviors, like how they rename duplicates when downloading the same file twice and such.

To debug your rules, first start with the preview. If the files don't match the rule you want there, then there's an issue with your rule conditions that you need to fix. The logs will show actual errors when executing, usually as a result of the actions.