-
-
Notifications
You must be signed in to change notification settings - Fork 20
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]: Status 500: RequestError [HttpError]: other side closed #287
Comments
Here's how we use the |
We're seeing this as well with the Databricks CLI: https://github.com/databricks/cli/blob/main/.github/workflows/release.yml#L121-L131. Is this a problem from |
VirtusLab/scala-cli#2689 (comment) |
I can confirm the issue in the today's release of Sandboxie Plus: RequestError [HttpError]: other side closed
|
Same on todays release of Strem
|
Is there any update about this bug? |
Is there an existing issue for this?
What happened?
What's happening
We are getting RequestError [HttpError] when releasing Scala CLI on winget with the
winget-releaser
action.We got this error on 2 subsequent releases up till now (details below).
Scala CLI tags on which it failed and the related
winget-pckgs
PRsv1.1.2
tag: winget release failed with the error above, PR towinget-pckgs
got created, it's still hangingwinget-pckgs
PR: New version: VirtusLab.ScalaCLI version 1.1.2 microsoft/winget-pkgs#135148v1.1.1
tag, winget release failed with the error above, PR towinget-pckgs
got created and then merged, seems to have been a false positive asv1.1.1
is available onwinget
winget-pckgs
PR: New version: VirtusLab.ScalaCLI version 1.1.1 microsoft/winget-pkgs#133549v1.1.0
and earlier releases have been green, so the issue started appearing withv1.1.1
Extra context
winget-releaser
failure duringUpdate Windows packages
step: RequestError [HttpError]: other side closed VirtusLab/scala-cli#2689 - corresponding Scala CLI issueThe text was updated successfully, but these errors were encountered: