Skip to content
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

Sync started failing on macOS Monterey #13

Open
TuggyNE opened this issue Nov 17, 2022 · 2 comments
Open

Sync started failing on macOS Monterey #13

TuggyNE opened this issue Nov 17, 2022 · 2 comments

Comments

@TuggyNE
Copy link

TuggyNE commented Nov 17, 2022

I set up auto-sync a few months ago (for some shared Org mode files) and it seemed to be running well since then. However, late last month it seems to have silently stopped working, perhaps due to some sort of software update. git auto-sync daemon add . and all other daemon commands seem to work fine, indicating that the repo is registered to synchronize and the daemon is running, but it doesn't actually make commits or push them. git auto-sync sync . fails with the cryptic error 2022/11/17 16:07:08 invalid checksum. I vaguely remember having some minor difficulties recently getting gpg and git to work correctly again after some changes, but AFAIK that's all working fine now (and manually committing and pushing from the synchronized directory has no problems).

Where would I find more troubleshooting information?

@TuggyNE TuggyNE changed the title Sync started failing on macOS Sync started failing on macOS Monterey Nov 17, 2022
@vHanda
Copy link
Contributor

vHanda commented Nov 17, 2022

Hmm, i can't remember now, but this doesn't yet support encrypted keys or gpg.

Regardless, silently failing sucks. Let me see if I can at minimum at least add proper error messages.

@TuggyNE
Copy link
Author

TuggyNE commented Nov 17, 2022

Strange, because when I set it up originally I'd been using git with signed tags by default for quite a while. And commits in this repo still aren't signed, even the manual ones. Maybe that's a red herring. There have doubtless been other updates as well.

Thanks for looking into this!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants