Degraded performance and upload failure when projects reach >200 versions #1253
Labels
1. bug
Something isn't working
2. backend
This issue/pr relates to an issue/change on the backend
needs testing
Observed/problematic behavior
I have a project on Hangar (https://hangar.papermc.io/William278/HuskHomes) with two channels; Alpha and Release.
I publish to the alpha channel continuously; every time a commit is made to my project, a version is published to Hangar via the API to this channel. This enables users to download bleeding edge versions if they so desire; only main releases are published to the release channel (in accordance with TOS)
I've now published about 200 versions to Hangar, and have noticed degraded performance as I continue to publish more; specifically:
Expected behavior
Hangar gracefully handles me having more than 200 versions on a project, lets me continue to upload new versions, and smoothly browse existing ones
Steps to reproduce
Have a project with over 200 versions, and attempt to upload another version, either through the API or the frontend.
You can also experience the timeout issue by going to https://hangar.papermc.io/William278/HuskHomes/versions and observing the errors in the bottom-right
Other
No response
The text was updated successfully, but these errors were encountered: