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
Currently, AllSpice Hub is at 1.19, where the team members endpoint is paginated with a 0-based index. This was fixed in 1.20 (go-gitea/gitea#24754) and the endpoing is 1-based as documented. Right now, py-allspice uses the 0-index, and when AllSpice Hub switches to 1.20 this will lead to duplicates in the list of team members. We'll have to change Team.get_members when we release 1.20.
The text was updated successfully, but these errors were encountered:
Thanks for finding this! Can you add a cron job to schedule the CI tests nightly? I think it'll help us preemptively catch issues like this (where we might update the application to 1.20, but forget to update py-allspice).
Currently, AllSpice Hub is at 1.19, where the team members endpoint is paginated with a 0-based index. This was fixed in 1.20 (go-gitea/gitea#24754) and the endpoing is 1-based as documented. Right now, py-allspice uses the 0-index, and when AllSpice Hub switches to 1.20 this will lead to duplicates in the list of team members. We'll have to change
Team.get_members
when we release 1.20.The text was updated successfully, but these errors were encountered: