Unexpected Internal Server Error 500 During GitHub Packages Deployment

[flutter-jihoon]

Select Topic Area

Bug

Body

Hello GitHub Community,

I am currently experiencing an issue while deploying Maven AAR packages built from Flutter to GitHub Packages. Specifically, I am encountering an unexpected Internal Server Error 500. Despite following the standard deployment procedures, the error persists and I am unable to successfully complete the deployment.

Additionally, I would like to note that this issue is only occurring when using GitHub Actions. Out of multiple AAR deployments, only a few are failing with this error, making it an intermittent problem. This is a recent issue that has suddenly arisen, and I am unsure of any changes that might have triggered it.

Thank you in advance for your assistance.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[Sheldan]

I am also experiencing issues, but nothing is reflected in https://www.githubstatus.com/ yet.

[msquillace]

I am having this issue as well when using the maven deploy plug-in to upload artifacts to Github packages. It only seems to happen from GitHub actions, it does not happen locally if I upload using maven deployer from my local machine. The problem is also not regular, it happens about three or four out of five times. I can see some of my artifacts being successfully uploaded.

[pcdavid]

We've had this too, for example here: https://github.com/eclipse-sirius/sirius-web/actions/runs/10219732660/job/28278579664, which fails during an mvn -B deploy -f packages/pom.xml step, after having successfully deployed part of the build artifacts.

Failure message:

Error: Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on project sirius-components-charts-parent: Failed to deploy artifacts: Could not transfer artifact org.eclipse.sirius:sirius-components-charts-parent:pom:2024.7.7 from/to github (https://maven.pkg.github.com/eclipse-sirius/sirius-web): transfer failed for https://maven.pkg.github.com/eclipse-sirius/sirius-web/org/eclipse/sirius/sirius-components-charts-parent/2024.7.7/sirius-components-charts-parent-2024.7.7.pom, status: 500 Internal Server Error -> [Help 1]

The exact same build sometimes works, sometimes fails, and when it fails it's not always on the same artifact.

[Sheldan]

I just had two releases succeed with contained a lot of modules. Yeah, there was a chance before as well, but I think it might be fixed, because if it works twice for that amount of modules (50+), I should get a lottery ticket.

[flutter-jihoon]

Yes, I think it works fine now