-
Notifications
You must be signed in to change notification settings - Fork 234
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
Fatal error uncaught exception after selecting default profile #1058
Comments
Side question: I also noticed the brew version of unison has no gui, is that right? I have to always manually download the release to get the gui version. |
Looks likely a legit bug for the tracker, but this is for bona fide bugs only, not help. Please read
and address brew questions to brew. |
Please read the bugs wiki page and:
|
I can't test or work on the Mac-native GUI, but it seems that the error is caused by the sync roots being unspecified. Normally, you'd get a proper error/usage message for this but it seems that the Mac-native GUI skips this validation. In other words, you shouldn't use the default profile (create another one), alternatively you should add the sync roots into the default profile configuration. You could also try the GTK GUI (what's called unison-gui in the release package), which should run on macOS (I guess you'd need to install GTK via brew). This is still a bug in the Mac-native GUI (it blindly assumes that if a profile is specified then the roots are also specified, without checking it). |
Homebrew has both GUI and CLI versions. λ brew search unsion
==> Formulae
unison ✔
==> Casks
unison |
Context
Hi all, I came to know unison from lra/mackup#1924, because I was exploring ways to backup any important application configurations that I use daily. My needs are simple, they can be configs such as vscode settings, slack preferences etc. Your generic stuff basically. I am still learning how to do this stuff for the first time.
Problem
It's my first time trying to use unison, but unfortunately I get this error. Let me know if I can somehow get you more logs.
Environment
Steps to reproduce:
Actual Results
I can consistently reproduce this bug.
Logs
The text was updated successfully, but these errors were encountered: