Noodlesoft Forums

Both ‘Rule → Preview Rule…’ and ‘Rule → Rule Status…’ indicate a match for my Rule ‘Rearrange’, but the Rule’s Action is NOT being performed or is being performed erratically as it evaluates the name of the file ‘+BrokerageStatement0531228353.pdf’; I turned on Debug and found this in the log:

Code: Select all

2022-06-16 19:49:09.363 hazelworker[5281] +BrokerageStatement0531228353.pdf: Rule Rearrange matched.
2022-06-16 19:49:09.363 hazelworker[5281] DEBUG: New rule signature. Executing actions.
Old signatures: (
)
New Signature:{displayBasename hazelMatchesPattern: (+,{hazelcustomtoken:5498:(5498):id0:cap},{hazelcustomtoken:YMD1:({year}:{month}:{dayOfMonth}):cap},22,{hazelcustomtoken:acct1:({digit:id0}:{digit:id0}:{digit:id0}:{digit:id0}):id0:cap}),{
} OR displayBasename hazelMatchesPattern: (+,{hazelcustomtoken:1099 Composite:(1099CompositeandYearEndSummary):sc0:id0:cap},{hazelcustomtoken:YMD2:({year}:{month}:{dayOfMonth}):cap},22,{hazelcustomtoken:acct2:({digit:id0}:{digit:id0}:{digit:id0}:{digit:id0}):id0:cap}),{
} OR displayBasename hazelMatchesPattern: (+,{hazelcustomtoken:1099Misc:(1099MISC):sc0:id0:cap},{hazelcustomtoken:YMD3:({year}:{month}:{dayOfMonth}):cap},22,{hazelcustomtoken:acct3:({digit:id0}:{digit:id0}:{digit:id0}:{digit:id0}):id0:cap}),{
} OR displayBasename hazelMatchesPattern: (+,{hazelcustomtoken:Brokerage:(BrokerageStatement):sc0:cap},{hazelcustomtoken:MDY:({month}:{dayOfMonth}:{year}):cap},{hazelcustomtoken:acct4:({digit:id0}:{digit:id0}:{digit:id0}:{digit:id0}):id0:cap}),{
} OR displayBasename hazelMatchesPattern: (+,{hazelcustomtoken:YE Gain Loss:(YearEndGainLossReporting):sc0:cap},{hazelcustomtoken:YMD4:({year}:{month}:{dayOfMonth}):cap},22,{hazelcustomtoken:acct5:({digit:id0}:{digit:id0}:{digit:id0}:{digit:id0}):id0:cap}),{
} OR displayBasename hazelMatchesPattern: (+,{hazelcustomtoken:Charitable:(CharitableGiftStatement):sc0:cap},{hazelcustomtoken:MDY2:({month}:{dayOfMonth}:{year}):cap},{hazelcustomtoken:acct6:({digit:id0}:{digit:id0}:{digit:id0}:{digit:id0}):id0:cap}),{
}}:{(rename:(
    "_",
    "{hazelcustomtoken:MDY2}",
    " Schwab -",
    "{hazelcustomtoken:acct1:sc0}",
    "{hazelcustomtoken:acct2:sc0}",
    "{hazelcustomtoken:acct3:sc0}",
    "{hazelcustomtoken:acct4:sc0}",
    "{hazelcustomtoken:acct5:sc0}",
    "{hazelcustomtoken:acct6:sc0}",
    "{extension:sc0}"
),{
})}
2022-06-16 19:49:09.363 hazelworker[5281] Caught exception in rule evaluation of file +BrokerageStatement0531228353.pdf: *** -[NSPlaceholderMutableString initWithString:]: nil argument
2022-06-16 19:49:09.363 hazelworker[5281] DEBUG: Tapping error retry sequence
2022-06-16 19:49:09.363 hazelworker[5281] ###main load address: 0x1056a9000
2022-06-16 19:49:09.363 hazelworker[5281] ###Hazel Core load address: 0x105984000
2022-06-16 19:49:09.363 hazelworker[5281] ###Noodle load address: 0x105ca5000
2022-06-16 19:49:09.363 hazelworker[5281] ###CK load address: 0x105864000
2022-06-16 19:49:09.363 hazelworker[5281] (
   0   CoreFoundation                      0x00007ff81a4ec7b3 __exceptionPreprocess + 242
   1   libobjc.A.dylib                     0x00007ff81a24cbc3 objc_exception_throw + 48
   2   Foundation                          0x00007ff81b27d9ee -[NSURL(NSURL) retain] + 0
   3   Foundation                          0x00007ff81b2e908f +[NSString stringWithString:] + 33
   4   HazelCore                           0x00000001059ef4a9 _isDateValue + 53642
   5   HazelCore                           0x00000001059efd0e _isDateValue + 55791
   6   HazelCore                           0x00000001059f6626 _isDateValue + 82695
   7   HazelCore                           0x00000001059f6036 _isDateValue + 81175
   8   HazelCore                           0x00000001059ecdb6 _isDateValue + 43671
   9   HazelCore                           0x00000001059f61cc _isDateValue + 81581
   10  HazelCore                           0x00000001059ecba5 _isDateValue + 43142
   11  HazelCore                           0x00000001059d1b17 errorFromOSAScriptErrorDict + 191975
   12  HazelCore                           0x00000001059b92bf errorFromOSAScriptErrorDict + 91535
   13  hazelworker                         0x00000001056afb9f hazelworker + 27551
   14  hazelworker                         0x00000001056b2615 hazelworker + 38421
   15  hazelworker                         0x00000001056b49f6 hazelworker + 47606
   16  dyld                                0x000000011196451e start + 462
)


Does this indicate a bug in Hazel?

Code: Select all

2022-06-16 19:49:09.363 hazelworker[5281] Caught exception in rule evaluation of file +BrokerageStatement0531228353.pdf: *** -[NSPlaceholderMutableString initWithString:]: nil argument

If you need additional logging or other information, how do I get it to you?

What else can I do to figure out why the Action is NOT occurring despite a match?

What version of Hazel are you running and are you on Intel or M1?

Mr_Noodle wrote:What version of Hazel are you running and are you on Intel or M1?

OS X Version 12.4 (Build 21F79)
Hazel Version 5.1.2 (Build 2274)
iMac (Retina 5K, 27-inch, Late 2015)
3.2 GHz Quad-Core Intel Core i5

Have a similar problem. Mac is Intel not M1 Hazel 5.1. Matched, no action (copying file if date created is today) from Synology NAS. Exported the rule and recreated and imported rule. Now the file from today is not even matched when doing rules status, of course no action if no match. Before recreating there was a rule match for the file but no action. Files have not changed in the folder.
Restarting Hazel makes no difference.

Thanks. This should be fixed in the next patch which is due in the coming week or so.

This should be fixed in the next patch which is due in the coming week or so.

Does your patch address both my issue and @roads’ or just one of our issues?

@roads needs to create a separate thread as it seems totally unrelated.

Mr_Noodle wrote:This should be fixed in the next patch which is due in the coming week or so.

Do you have revised projected time for releasing this patch?

I'm hoping next week but it depends on some other issues.

Mr_Noodle wrote:I'm hoping next week but it depends on some other issues.

Ok.

This bug is holding up my work. But it is much better to take the time you need to fix it once rather than "fixing" it quickly only to have to come back and fix it again.

Thank you for the update.

If it's urgent and you are willing to run a test build, email in to support and I'll send you a link.

Mr_Noodle wrote:If it's urgent and you are willing to run a test build, email in to support and I'll send you a link.

Thank you for the offer, but I’ll wait for it a fully tested version.

Seems to be working now.

Thank you.