-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Include fs stats and mode in zip archive, fix "too many open files" error #1723
base: main
Are you sure you want to change the base?
Include fs stats and mode in zip archive, fix "too many open files" error #1723
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is the right one that works for me unless you know it works for me good so zip hope you figure the problem that you got going on read read you get it
actions/upload-artifact#485 looks relevant here, and could be easily fixed in the same PR by using |
Commit 5f62f1e should fix actions/upload-artifact#485. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Looking at file documentation this PR should fix actions/upload-artifact#485
@bethanyj28 - It looks like you've been doing recent work on the |
@SrRyan @yacaovsnc You recently reviewed PRs touching this part of the code (#1678 and #1724 respectively). Could you take a look at this PR? It's intended to fix the seventh-most-upvoted issue in actions/upload-artifact and also a recent issue that prevents uploaded artifacts from containing more than about 8,000 files. The latter has a workaround, using If you're not the right people to contact about code review, would you let me know whom I should be talking to? Thank you. |
@bdehamer - Can you tell me who is the right person to review PRs in this repo? I've asked multiple GitHub team members so far, with no response yet from anyone. This should be a pretty straightforward review, and one of the bugs it fixes is the sixth-most upvoted issue in its tracker. (Used to be seventh-most, but one was closed recently). I'm surprised it's been so hard to get a bugfix even looked at, let alone merged. |
@konradpabjan - Your GitHub profile says you're working on GitHub Actions, and you created one of the bugs this PR is supposed to fix. Could you let me know how I can get this bugfix reviewed by a GitHub Actions team member, so that the "Too many open files" fix can finally be merged? |
https://github.com/orgs/actions/people one of these people will probably need pinged |
@joshmgross - Could I ask you to take a look at this PR? It's intended to fix the sixth-most-upvoted issue in actions/upload-artifact and also a recent issue that prevents uploaded artifacts from containing more than about 8,000 files. The latter has a workaround, using P.S. I apologize for the random ping, but as you'll see from the comment history, this PR has been open for three months and I've had no success yet in getting anyone from the GitHub Actions team to look at this bugfix. Even a "Sorry, we don't accept outside PRs for this code" message would be fine, as long as some bugfix for actions/upload-artifact#485 goes in. |
👋 Hey @rmunn, I'll check internally to see what we can do here - my best guess is it will be safer to separate out the bug fix here from the feature to support file permissions. We do accept outside PRs, but generally speaking we're a bit limited on new features as that increases the maintenance burden of the action (every new feature is something we will have to support in perpetuity). |
Thanks for responding. This PR was originally based around supporting file permissions, which is a feature request that's more than four years old at this point (actions/upload-artifact#38, actions/download-artifact#14). I then added the "too many open files" fix because I was already touching the same code, and why increase the maintenance burden by asking an overworked team to review two separate PRs? But if, in fact, the maintenance burden would be reduced by splitting the PR in two, then I'll do it that way. I'll open a new PR for the fix to actions/upload-artifact#485, and keep this one focused on its original intent, the .zip file permissions loss. (Which I consider a bugfix, not a new feature, but at least it has a workaround: create a .tar file and upload that. Though that then runs into actions/upload-artifact#426 and actions/upload-artifact#39, but those are annoyance-level bugs rather than blockers). |
@joshmgross - I've created #1771 for the EMFILE fix without the zip file permissions bugfix. |
This should allow Unix file permissions to be included in the zip file created by upload-artifact, fixing actions/upload-artifact#38 and probably actions/upload-artifact#37 as well.
Fixes #1722.
Fixes actions/upload-artifact#485.
This is basically #1609, rebased against the current state of the
main
branch. But #1609 did not include themode
property in its call tozip.append
, and my research suggests thatmode
is needed to actually include the permissions in the zip file.