-
Notifications
You must be signed in to change notification settings - Fork 66
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]: octokit.rest.repos.downloadZipballArchive fails with unexpected 500 HTTP error #461
Comments
👋 Hi! Thank you for this contribution! Just to let you know, our GitHub SDK team does a round of issue and PR reviews twice a week, every Monday and Friday! We have a process in place for prioritizing and responding to your input. Because you are a part of this community please feel free to comment, add to, or pick up any issues/PRs that are labeled with |
Unfortunately that error doesn't give any information... All it says is that the socket was closed unexpectedly I would suggest using streams instead, see example here: #12 (comment) It shouldn't matter what platform it's running on at least for this kind of code. I can't help you on that one |
Thanks for the suggestion. |
I have no idea why you're getting HTTP 500 errors only on Linux |
It's very weird. |
I'm also seeing this error when making a const file = await octokit.rest.repos.getContent({
owner,
repo,
ref,
path,
mediaType: { format: "raw" },
});
This is running inside the |
What happened?
Using
ocotokit.reset.repos.downloadZipballArchive
often fails with a 500 HTTP error on Linux.I use this api in libsdl-org/setup-sdl here.
In this action workflow, the
libsdl-org/setup-sdl
action is used on 3 platforms (macos, Window and Linux).It succeeds on Windows and macOS, but always fails on Linux.
Versions
@octokit/rest 21.0.1
octokit 3.2.1
node 20.13.1
Relevant log output
Code of Conduct
The text was updated successfully, but these errors were encountered: