Noodlesoft Forums

I updated tonight, and my rules were running fine before that. I had kept the console open, and noticed the following excerpt upon updating and re-running my rules. I have renamed my rules to make it easier to see which one it's referring to, and have also enabled Debug Mode, so once I have further information I will post a reply.

Code: Select all

2018-12-17 02:51:47.035 hazelworker[1381] 2017-05-15 14.53.30.jpg: Rule Move Photos to Google Photos matched.
2018-12-17 02:51:50.569 hazelworker[1381] [File Event] File moved: 2017-05-15 14.53.30.jpg moved from folder /Users/user/Dropbox (Personal)/Camera Uploads/2017/05 to folder /Volumes/GoogleDrive/My Drive/Google Photos.
2018-12-17 02:51:50.570 hazelworker[1381] Caught exception in rule evaluation of file 2017-05-15 14.53.30.jpg: [NSMachPort sendBeforeDate:] destination port invalid
2018-12-17 02:51:50.570 hazelworker[1381] ###main load address: 0x10ad46000
2018-12-17 02:51:50.570 hazelworker[1381] ###Noodle load address: 0x10ae69000
2018-12-17 02:51:50.570 hazelworker[1381] ###CK load address: 0x10ae2e000
2018-12-17 02:51:50.570 hazelworker[1381] (
   0   CoreFoundation                      0x00007fff2a544ecd __exceptionPreprocess + 256
   1   libobjc.A.dylib                     0x00007fff565fc720 objc_exception_throw + 48
   2   CoreFoundation                      0x00007fff2a544cff +[NSException raise:format:] + 201
   3   Foundation                          0x00007fff2c8454f1 +[NSMachPort sendBeforeTime:streamData:components:to:from:msgid:reserved:] + 1539
   4   Foundation                          0x00007fff2c844ed8 -[NSMachPort sendBeforeDate:msgid:components:from:reserved:] + 96
   5   Foundation                          0x00007fff2c844c66 -[NSConnection _sendBeforeTime:coder:doAuthenticationCheck:] + 357
   6   Foundation                          0x00007fff2c8e92a6 -[NSConnection sendInvocation:internal:] + 1202
   7   CoreFoundation                      0x00007fff2a4e687e ___forwarding___ + 780
   8   CoreFoundation                      0x00007fff2a4e64e8 _CF_forwarding_prep_0 + 120
   9   hazelworker                         0x000000010adad5f7 hazelworker + 423415
   10  hazelworker                         0x000000010adad3c8 hazelworker + 422856
   11  hazelworker                         0x000000010adad0fc hazelworker + 422140
   12  hazelworker                         0x000000010ad67da3 hazelworker + 138659
   13  hazelworker                         0x000000010ad8bc1b hazelworker + 285723
   14  hazelworker                         0x000000010ad4dd98 hazelworker + 32152
   15  hazelworker                         0x000000010ad50f87 hazelworker + 44935
   16  hazelworker                         0x000000010ad532af hazelworker + 53935
   17  libdyld.dylib                       0x00007fff576caed9 start + 1
   18  ???                                 0x0000000000000003 0x0 + 3
)


Interestingly, I've currently got Hazel stopped, and this rule seems to continue to run. I'm not sure why, seeing as the rule itself is also paused. I have rebooted my laptop as well, and it doesn't seem to have stopped it running. This behaviour was evidenced before the update too.

I think you may have two Hazel's installed. Launch System Preferences. Go to "Users & Groups", then "Login Items". Is HazelHelper listed there more than once? If so, throw away both copies (do not throw away associated files if prompted), reboot, then reinstall Hazel.

Hmmm, no there's only one HazelHelper. How odd.

It does sort of seem to have fixed itself after like the 5th reboot, so I'll keep an eye on it.