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

GitHub says "Roam Research backup: All jobs have failed" after any .md file changed via GitHub #1

Open
kolanuts opened this issue Jan 12, 2021 · 0 comments
Labels
bug Something isn't working

Comments

@kolanuts
Copy link

Describe the bug
Within one minute after saving a change to a Markdown file in _pages in GitHub, an error email from GitHub comes:

grafik

Clicking through to GitHub, see this:

grafik

Some 6 minutes later, (in the past, within a minute) get another email:

grafik

This has occured multiple times, whenever I changed any Markdown file via GitHub.

To Reproduce
Steps to reproduce the behavior:

  1. Change index.md or about.md directly within the GitHub site via a browser (Firefox).
  2. Check live site using Maxime Vaillancourt's template after a minute: Changes were published successfully.
  3. Get an email from GitHub notifications saying "[kolanuts/digital-garden] Run failed: Roam Research backup - main (f1558ec)"

Expected behavior
I'd expect there to be no failure message, and for the backup to succeed.

Traceback
grafik

Run roam-to-git --debug notes/ and report what you get.
It should open a Chrome front-end, an do the scrapping. The repository content will not be modified. If applicable, add screenshots to help explain your problem.

  • OS: Win10
  • Do you use Github Action? Yes
  • Do you use multiple Roam databases? Yes, but only 1 is connected with my repo of course
  • Does roam-to-git use to work for you? (This should be "Did roam-to-git work for you previously?") I think this has happened every time, but the updates are still pushed live!
  • Does some backup runs are still working? (This should be "Are some backup runs still working?") I think... not? Not sure how to see this. But screenshot under Traceback suggests backups are not working.
@kolanuts kolanuts added the bug Something isn't working label Jan 12, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant