Closed mroi closed 10 months ago
Looks like evidence of a bug so this is legit in the tracker. For discussion/help please ask on unison-hackers@.
Could you please try a debug build from https://github.com/bcpierce00/unison/actions/runs/5895042600 (I don't have a way to test on macOS myself but this will hopefully fix the bug)
Wow. Blind debugging. And even better: It works. I tested all three app bundle artifacts. All work.
Found the same problem, which makes sense given that the last release is previous to this issue. Any plans for a new release?
There is a release candidate build available at https://github.com/bcpierce00/unison/actions/runs/7902642581 (scroll all the way to the end)
Thank you. Actually I tried that one before commenting here, and though it ran, it displayed a weird empty dialog at the end. (Maybe because my profile has batch = true
? no idea)
Then I tried running the CLI again and got an error that I couldn't find any info about (Fatal error: Property lists: paths not yet registered!
), which stopped unison from doing anything. After a good while trying stuff I ended up deleting the archive files to be able to run unison again.
So I'd say there's a bug somewhere, not sure if in that GUI or what. I suspect unison renamed a folder as part of the sync and then tried to apply changes to the old folder.
Thank you. Actually I tried that one before commenting here, and though it ran, it displayed a weird empty dialog at the end. (Maybe because my profile has
batch = true
? no idea)
Please report a separate issue if you can reproduce this, possibly in the mailing list if it's more a question "is this a bug?". Provide a screenshot of the weird dialog.
Then I tried running the CLI again and got an error that I couldn't find any info about (
Fatal error: Property lists: paths not yet registered!
), which stopped unison from doing anything. After a good while trying stuff I ended up deleting the archive files to be able to run unison again.
This is unrelated, as this is a result of downgrading Unison and running an older version with upgraded archives.
I was trying the extended attributes support for the first time, when I noticed an oddity: For the same build (my own as well as the release tarball), the text UI would sync extended attributes just fine, while the graphical UI would refuse. The error I get is an alleged lack of server support for![Bildschirmfoto 2023-08-16 um 20 12 18](https://github.com/bcpierce00/unison/assets/1226345/c3231794-5ba0-403b-a7b2-e5058c877e60)
Sync: xattr
, which is simply untrue.Again, the same binary syncs extended attributes fine with the text UI.
The debug logs from both versions look like this:
I think the macOS graphical UI lacks some steps in its setup compared to the text UI as the feature information for the roots is never completely shown. From the code, I think the relevant part may be:
Globals.installRoots2
is used by the macOS graphical UI (exclusively, it seems)Globals.installRoots
is used by the text UIBut my OCaml skills are way below understanding the details here. Any advise what I can try?