Closed shiruken closed 1 year ago
yes it is. apologies. I'm in the process of fixing that, and should hopefully have it back in working order either tonight or tomorrow morning (UK time)
In the meantime, you can change line 35 of .github/workflows/get_context.yml
in your fork like so:
- run: python find_posts.py --access-token=${{ secrets.ACCESS_TOKEN }} --server=${{ vars.MASTODON_SERVER }} --reply-interval-in-hours=${{ vars.REPLY_INTERVAL_IN_HOURS || 0 }} --home-timeline-length=${{ vars.HOME_TIMELINE_LENGTH || 0 }} --max-followings=${{ vars.MAX_FOLLOWINGS || 0 }} --user=${{ vars.USER }} --max-followers=${{ vars.MAX_FOLLOWERS || 0 }} --http-timeout=${{ vars.HTTP_TIMEOUT || 5 }} --max-follow-requests=${{ vars.MAX_FOLLOW_REQUESTS || 0 }}
But you will need to revert those changes when I finish up the next release.
Really sorry, this is entirely my fault.
No worries, I was just checking it out and ran into the errors and wanted to make sure you were aware of it.
This is fixed on v4.1.1
Forked repository as of c587e0907aceb6506f235f1103c68f44e5e090b5 fails with the following error message: