Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Error when removing a version of a package #1077

Open
1 task done
kris6673 opened this issue Feb 13, 2025 · 1 comment
Open
1 task done

[Bug]: Error when removing a version of a package #1077

kris6673 opened this issue Feb 13, 2025 · 1 comment
Assignees
Labels
bug Something isn't working help wanted Extra attention is needed

Comments

@kris6673
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

What happened?

Tried removing a version where it's the only version available in the repo. It threw the following error, but the PR was created with the reasoning text just fine. Soooo, now I'm just doing as the command line told me:

PS C:\Temp> komac remove 3.3Kontakt -v 5.10.3.9083
Packages should only be removed when necessary
Latest version of 3.3Kontakt: 5.10.3.9083
> Give a reason for removing 3.3Kontakt version 5.10.3.9083 Vanity link has updated to new version. See PR #229040 for
pdate
> Would you like to make a pull request to remove 3.3Kontakt 5.10.3.9083? Yes
Error:
   0: Something went wrong while executing your query. This may be the result of a timeout, or it could be a GitHub bug. Please include `A6A9:30387D:D0A6BD:D59A89:67AE161F` when reporting this issue.

Not sure if you can do anything about it? :D

@kris6673 kris6673 added bug Something isn't working help wanted Extra attention is needed labels Feb 13, 2025
@russellbanks
Copy link
Owner

The Something went wrong while executing your query error is what GitHub returns to the call. Originally I had the issue of the error message not being very clear so I started returning what GitHub responds with. With this error, the issue is on GitHub's side and would likely either work fine later on or work if you retried it straight away. The reference that it provides when reporting the issue would actually be if it were reported to GitHub support.

This essentially would be the same as what we were getting in #1009.

I suppose I should probably not output this particular error specifically seeing as I can't do anything with that reference it returns (and it implies that I'm the one to report it to). As for working around it, I could potentially implement retry functionality but I so far haven't already done that because often if GitHub returns that then it probably will just keep returning it.

I'll keep this issue open seeing as this issue keeps cropping up and see about implementing retry functionality.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants