-
Notifications
You must be signed in to change notification settings - Fork 29
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
Error: Process completed with exit code 127 #72
Comments
You will need to set
|
If you've correctly set |
That's the thing; it is set up correctly (so far as I know) as a repository secret. I even tried updating it just now and forcing the automation to run, and it failed again. I know there must be something I'm doing wrong but I can't figure it out for the life of me. |
Yep, that all looks correct. Are you still getting the same error as the initial post? There are some other errors there – maybe you just need to sync your fork with the original repo to pull down any more recent commits? |
Can you share the full log of the GitHub Action? One thing I did so that I could test it more easily is add the name: Zotero to Readwise Automation
on:
push:
branches:
- master
schedule:
- cron: "0 3 * * *" # Runs at 03:00 AM (UTC) every day (Check https://crontab.guru/)
workflow_dispatch: |
I think some of the secrets may be configured incorrectly based this line:
You may also want to update your last comment as I think it contains a password or API key. Can you share a screenshot (with a fake value in) of exactly what values you're using in the repository secrets? I suspect that there are some extra quotes or perhaps special characters like exclamation points or something like that that are interfering with your setup. |
In particular, this line in the
You could try changing it to
I am not an expert on how GitHub provides these secrets, they may already be escaped, but I suspect they aren't. This is at least where I'd look next for myself. |
Thanks for the heads up. I wasn't thinking when I posted that. Checked the values. None of them include any special characters. Just letters and numbers. I'll try updating the automation.yml with the extra quotes to see if that helps. |
In case it helps, here is a list of special characters in Bash:
|
None of those are in there. Just A-Z (both cases) and 1-9. Made the update to automation.yml and am now getting this: Readwise: Push 553 Zotero annotations/notes to Readwise... Traceback (most recent call last): During handling of the above exception, another exception occurred: Traceback (most recent call last): |
Bummer. At least now we've got the app running – this may be some issue with particular characters in a Zotero highlight or a text encoding issue? I'm really just guessing now. I think we've reached the limit of what I can help with without knowledge of the internals of this app. The next step I'd suggest is trying to get it running locally. Hopefully this will give you the same error and then you'll be able to dive in and debug what's happening on your local machine. |
One final thought – and this might be way off – are there any new lines in your secrets? Any blank spaces at the beginning or end? I assume GitHub simply dumps out the contents of the secret which may be causing some errors. |
Another good idea but nope. Updated them all to be sure. |
So interestingly, I tried to run the original Python script and got the following error:
I am trying to figure out what I could have possibly done wrong with Readwise. The other interesting thing is nothing gets written to the .json file that it supposedly writes everything to. So strange. |
I keep getting this error when I try to run the automation. As shown in the instructions, I set up the secrets, but it seems to be looking for a "zotero_library_id" which wasn't one of the three. Did I miss something?
Researching the error suggests that either (a) something is missing or (b) the script doesn't have other permissions it needs to run. Option b seems unlikely so I'm stuck on the hypothesis that it is option a, but after starting from a fresh fork, replacing the secrets, and generally doing everything I can think of, I'm stuck.
The text was updated successfully, but these errors were encountered: