Hazel 5 – lots of issues

Hi,

is it just me, are is using the interface of Hazel 5 a little disaster?
Look at this video: https://share.getcloudapp.com/d5uPYNLr.
Trying to move a rule around, or trying to delete a rule simple fails.

Could not get it to video: but the interface often "freezes" on me, so I have to restart Hazel.

Using the "Check status of current rules" window often does not appear when clicking the toolbar button...
I'm seriously considering downgrading. This is not what I expected of Hazel 5... Or am I missing something?

PS: running on Big Sur, but I notice the same issues on Catalina.

Regards,
—Roger

Can you provide logs? It seems clear there's an internal crash of sorts.

- Launch Console
- Enter Hazel in the search field and hit return
- Trigger the bug
- Send me the resulting log messages

I was able to trigger the "move rule" issue again.
Question is, which logs do you need? Console has a couple of them. See here: https://share.getcloudapp.com/7Kubvqwk.
I added below the one from earlier today (https://share.getcloudapp.com/YEuQKBYY).
Here the list of Diagnostic Reports (https://share.getcloudapp.com/GGu28EgB).
It seems to me that the interface issues are not generating any logs...

Click on the entry under Devices. It usually is what is selected by default when you launch Console.

Correct. But as that one was/is empty, with or without the search for Hazel, I sent the other ones...

Did you click the "start streaming" button? It won't start logging until you do that.

Here the video of what I was doing (trying): https://share.getcloudapp.com/v1u4ln9g.
And here the streaming Console info: https://share.getcloudapp.com/mXu5jvQK.

What is happening: delete is not working, and I cannot move the rule out of the if statement.

Thanks for that. I think I have enough to go on now.

Small addition: Hazel crashes while linking an existing rule file.
Here the crash output: https://share.getcloudapp.com/NQuKb96Z

Small addition: Hazel became complete unresponsive. I could only switch windows (main windows and the rules status checker), but could not close them or control them.
This occurs (very) often.
Solution is to close via the Quit option in the dock. The Hazel menu is at that moment also unresponsive.
Here the console output: https://share.getcloudapp.com/v1u4lG6q.

When moving a Finder Folder (with some rules attached to it) to a Folder created in Hazel, the rules disappeared.
This error message was shown: https://share.getcloudapp.com/7KubvwvX.

After the above, when trying a recreate the lost rules, I got this error message: https://share.getcloudapp.com/7Kubvw2X.

Trying to add a new rule (after starting – again – from scratch). Clicking the Add Rule button does not do anything: https://share.getcloudapp.com/QwubYy9n.

The console export: https://share.getcloudapp.com/geuoZDb2

Duplicating a rule is grayed out: https://share.getcloudapp.com/L1uO42Wq.
Makes sense if one cannot create a new rule...

Been able to use Hazel 5 all day long, and only had to Force Quit it a couple of times. All these were due to using the Rules Preview window.
Other aspects have been more stable.

Pointer in the issue direction: I switched off "Optimise Mac storage". Using this option has caused me other headaches, and I assume Hazel also has some issues with it...

Hmm, my response didn't seem to make it so typing this out again.

First off, consider emailing this stuff in instead of posting it. Chances are no one else on these forums will look at the log outputs you are sending and derive anything from them. Plus I check email much more often. This is particularly important this weekend as I'm planning a release tomorrow and only happened to check this thread.

The crash for the syncing rule doesn't seem right. It looks like it happened when adding a new folder, not when trying to connect it to an existing sync file. It could be that the addresses in the trace are incorrect. Can you repeat this on demand? If so, can you email in the sync file you are using?

Unresponsiveness may be due to a crash in the rule status. It's hard to tell from your logs as it's missing info. For future reference, at certain points (startup being one), Hazel will log output that looks like "######<<<something>>> load address: <<<stuff>>>". I'll need those lines to decipher any crashes that get logged later during that run. Those values change each run so they need to be matched up.

When moving a folder, were you adding a folder that already exists in Hazel? If so, that will cause problems. It should be fixed in the patch tomorrow.

For the add rule stuff, same issue regarding needing those load addresses. If you can replicate the bug, please do so, and send me the log lines with the load addresses along with the rest of the log.

As mentioned, I'm doing a release tomorrow so if you want any chance of these being fixed for that release, please email the info ASAP.