Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Backup fails - may be dupe of #46 & #47
See original GitHub issueDescribe the bug A clear and concise description of what the bug is.
Backup from actions has begun to fail repeatedly after 200+ successful commits.
To Reproduce Steps to reproduce the behavior:
-
Either allow Git Action to run as scheduled or manual run Git Action
-
See error in Gist here: https://gist.github.com/jmsidhu/875f9f89d5d8592cd463791168aa697c
Expected behavior Expected action to run per design
Traceback https://gist.github.com/jmsidhu/875f9f89d5d8592cd463791168aa697c
Run roam-to-git --debug notes/ and report what you get.
Not quite sure how to do this
Please complete the following information:
- OS: Win10 & iOS
- Do you use Github Action? Yes
- Do you use multiple Roam databases? No
- Does roam-to-git use to work for you? It used to
- When precisely did it stopped to work? This morning, 9/15
- Does some backup runs are still working? Consecutive backups are failing
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I am also having the same issue. I get error notification by email: Run failed for master (xxxxxxx). And an annotation: Process completed with exit code 1.
Like other posters, have had no problems for many commits, but suddenly it’s failing.
The backup errors should be fixed by #92 🍾.
I’m closing that issue, but feel free to re-open it if you get new errors.