Noodlesoft Forums

Hi. App sweep has recently started failing for me. Looking at the logs it appears that the failure has to do with my OneDrive, as it contains this error:

2024-12-02 09:34:48.182 hazelworker[69468] Received error while processing file /Users/kfitz/Library/CloudStorage/OneDrive-[InstitutionalInfo]/.Trash: Error Domain=NSCocoaErrorDomain Code=256 "The file “.Trash” couldn’t be opened." UserInfo={NSURL=file:///Users/kfitz/Library/CloudStorage/OneDrive-[InstitutionalInfo]/.Trash, NSFilePath=/Users/kfitz/Library/CloudStorage/OneDrive-[InstitutionalInfo]/.Trash, NSUnderlyingError=0x600000525ce0 {Error Domain=NSPOSIXErrorDomain Code=11 "Resource deadlock avoided"}}

Hazel appears to try to process the trash three times, dropping this error three times, and then says "Done processing folder Trash," but it hasn't actually recognized that there's an app in my trash. According to my system settings, Hazel has full disk access, but is there something I need to do in order to ensure that Hazel can open my OneDrive trash and process the rest of what's in my Finder trash?

Are the files (including the trash) actually local to your drive? You have to make sure everything is downloaded locally for Hazel to work.

Yes and no? I have a ton of OneDrive files that have been shared with me that I have not allowed to download to my local machine. I've just set OneDrive to download everything, but I'm still getting the error. I'm not at all sure how I would get OneDrive's Trash file/folder to be local, as it's not findable even when I show hidden files.

I'll also add that I have a second computer with this same setup -- OneDrive set to keep only selected folders locally -- and while the same error pops up in the log file App Sweep works perfectly. So this does not seem like a OneDrive-related issue.

I'd look into configuration differences between the two machines then.

There shouldn't be configuration differences that affect Hazel/App Sweep.

After several uninstall/reinstall cycles and a couple of reboots, the OneDrive error has disappeared from the logs. I just tried to move the app I'm trying to remove to the trash again, and this time got this error:

2024-12-03 09:18:09.636 hazelworker[17174] Could not resolve path for bookmark data: Error Domain=NSCocoaErrorDomain Code=259 "The file couldn’t be opened because it isn’t in the correct format."

Does that lead anywhere more helpful?

That error is probably irrelevant. What is the actual behavior now?

kfitz wrote:After several uninstall/reinstall cycles and a couple of reboots, the OneDrive error has disappeared from the logs.

I too have found the pesky OneDrive Code=11 "Resource deadlock avoided" error in my logs after I upgraded to v6 last night, and today I fiddled with the sync folders and found out the sync (or was it shared?) folder that created the .Trash directory which was generating the error.

After moving the affected files on the share to an external drive, and removing it from the preferences panel, the OneDrive error is gone.

I have also gained in CPU cycles, so maybe that error was also creating some sort of deadlock which was slowing down my machine... Hazel to the rescue, albeit indirectly!

Thanks @Mr_Noodle!

Bye, Luca

Is there a pattern to the affected files?

lucaberta wrote:

kfitz wrote:After several uninstall/reinstall cycles and a couple of reboots, the OneDrive error has disappeared from the logs.

I too have found the pesky OneDrive Code=11 "Resource deadlock avoided" error in my logs after I upgraded to v6 last night, and today I fiddled with the sync folders and found out the sync (or was it shared?) folder that created the .Trash directory which was generating the error.

I would love to hear more about how you figured out what folder was creating the .Trash directory. I've been fighting with this for weeks and cannot figure it out.