You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The GitHub Action to run periodic updates broke a couple days ago. The Action runner was interrupted by a 6 hour TTL, inconclusive. The CLI seems to hang indefinitely in calling the API. Playing around with the code a bit I was able to at least get the first 40 (probably standard page size) results, but nothing more.
Expected
Correctly return the list of 40+ people following my profile to store in .txt
Anything else?
I've disabled the Action in the meantime, while I try to gather more information. There was no recent code change on my side or the library, that would warrant this change in behaviour, nor did the mastodon instance version change in the time frame where it broke.
The text was updated successfully, but these errors were encountered:
Just enabled the workflow again and it ran through successfully on an old failed attempt. Hachyderm updated to v4.1.2 and for some reason this changed the outcome. Since Hachyderm was running the previous version for longer than the workflow has been failing I'm unsure why this works again. Will leave it open for now to see that the next cron run-through is successful as well.
It seems the pagination might be broken, will have to dig a little bit to find out why.
Possibly related: mattn/go-mastodon#161
What is happening?
The GitHub Action to run periodic updates broke a couple days ago. The Action runner was interrupted by a 6 hour TTL, inconclusive. The CLI seems to hang indefinitely in calling the API. Playing around with the code a bit I was able to at least get the first 40 (probably standard page size) results, but nothing more.
Expected
Correctly return the list of 40+ people following my profile to store in .txt
Anything else?
I've disabled the Action in the meantime, while I try to gather more information. There was no recent code change on my side or the library, that would warrant this change in behaviour, nor did the mastodon instance version change in the time frame where it broke.
The text was updated successfully, but these errors were encountered: