Random stalls when running on large directories

[aussiesmith]

bitrot normally shows progress as a running percentage shortly after checking bitrot.db integrity.
This running percentage always appears quickly for relatively small directories.

For large directories like my home directory on macOS 12.6.1, bitrot may or may not show this running percentage. When it does show it, all is well and bitrot executes as expected. When it does not show it (most of the time), bitrot stalls right after integrity checking and may never complete its execution.

I am a newbie in Python so cannot readily investigate though I could help pinpoint the issue with instructions.

[ambv]

What Python version are you using bitrot with?

[aussiesmith]

What Python version are you using bitrot with?

3.11, and I have bitrot installed at:
/Library/Frameworks/Python.framework/Versions/3.11/bin/bitrot

[rwoodpecker]

Same issue with python 3.10.3 (macOS 13.1) on larger directories. Reverting to python 3.8.16 resolves the issue for me.

[aussiesmith]

Reverting to python 3.8.16 resolves the issue for me.

Not for me :-(

[ambv]

I can reproduce this on macOS 12.6.1 when you're using it on iCloud Drive or Dropbox. The problem is that the tool touches all files on this virtual file system, and for at least some of those files iCloud Drive or Dropbox blocks to check on the server side whether the file is up-to-date. This happens even if you have everything downloaded locally, which is pretty weird.

Which folders are you running bitrot on?

[aussiesmith]

I am running it on my home folder. Upgrading to macOS 13.2.1 appears to have reliably solved the issue...