-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Single named colored tag gets restored as named colored tag + generic tag with color name #56
Comments
I just tried to reproduce this and was not able to. In my case, the |
Ok and thanks for looking into this. |
This last two commits were really for #57 -- still working on reproducing this one. |
@all-contributors please add @porg for bugs, ideas |
I've put up a pull request to add @porg! 🎉 |
@porg, idk if it helps, but I had a similar issue while manually adding/removing Finder tags via a python script. In my case the issue was that I had a stale "com.apple.FinderInfo" xattr which stored the color info in addition to the regular Finder tag ("com.apple.metadata:_kMDItemUserTags" xattr). So when I removed the Finder tag (which had color) I got the standalone/generic color tag (from "com.apple.FinderInfo"). Removing the stale "com.apple.FinderInfo" xattr solved the issue in my case. |
@jkscx Not yet conducted any practical tests but from theory it sounds very plausible that the storage of the very same attribute at different metadata positions which needs syncing at each transaction can result in out of sync states if something is done improperly. |
Btw, a simple GUI tool which helped me inspect the xattrs of the file and find the issue in my setup is xattred from the macOS guru eclecticlight, in case you're interested. Simpler than viewing the xattrs via the command line and automatically decodes the binary plist of the Finder tags xattr. |
Still the bug as in the description above is valid.
|
@porg thanks for the update. I just tried to replicate this using your steps with macOS 13.1 and python 3.11.2 but could not replicate it. Will keep open as you're still seeing it. I did find another bug in the backup code while testing this that could cause backups to be corrupted on Ventura so I recommend upgrading to 1.3.0 |
Reproduction
Environment
The text was updated successfully, but these errors were encountered: