10000 cache: unlock zstd long mode and add support for `zstd --adapt` by smorimoto · Pull Request #1772 · actions/toolkit · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

cache: unlock zstd long mode and add support for zstd --adapt #1772

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

smorimoto
Copy link
Contributor
@smorimoto smorimoto commented Jul 23, 2024

If I remember correctly, we had that support before, but somehow it seems to have been removed at some point. This PR not only brings it back to keep the cache toolkit fast, but also "actually" enables long mode as described below.

At least the official GitHub Actions images have fairly new zstd installed on all platforms, so once merged we get all the benefits.

Comment on lines -105 to +114
if (versionOutput === '') {
if (version === null) {
return CompressionMethod.Gzip
} else {
} else if (semver.lt(version, '1.3.2')) {
return CompressionMethod.ZstdWithoutLong
} else if (semver.lt(version, '1.3.6')) {
return CompressionMethod.ZstdWithoutAdapt
} else {
return CompressionMethod.Zstd
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should also fix this bug, as it seems we have not actually been able to use long mode yet.

@@ -207,6 +207,7 @@ async function getDecompressionProgram(
// Used for creating the archive
// -T#: Compress using # working thread. If # is 0, attempt to detect and use the number of physical CPU cores.
// zstdmt is equivalent to 'zstd -T0'
// --adapt: Dynamically adapt compression level to I/O conditions.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@smorimoto smorimoto marked this pull request as ready for review July 23, 2024 13:28
@smorimoto smorimoto requested a review from a team as a code owner July 23, 2024 13:28
@smorimoto smorimoto force-pushed the zstd branch 2 times, most recently from 15cc910 to 2faac2a Compare July 23, 2024 13:59
@smorimoto smorimoto requested a review from a team as a code owner July 24, 2024 14:08
@smorimoto
Copy link
Contributor Author

Ready to merge!

@smorimoto
Copy link
Contributor Author

Gentle ping @robherley

@smorimoto
Copy link
Contributor Author

@robherley ping

@smorimoto
Copy link
Contributor Author

@nebuk89 How do we move this forward?

@smorimoto
Copy link
Contributor Author
8000

Gentle reminder

@smorimoto
Copy link
Contributor Author

@joshmgross ping

@smorimoto
Copy link
Contributor Author

ping @joshmgross

@joshmgross
Copy link
Contributor

👋 Hey @smorimoto,

Thank you for this change!

I don't think we have capacity to fully validate and test this change at the moment, but I'll keep in mind in the future when we're ready to invest more in this cache package.

@Link- Link- self-assigned this Dec 2, 2024
@smorimoto
Copy link
Contributor Author

Gentle ping

Signed-off-by: Sora Morimoto <sora@morimoto.io>
@smorimoto smorimoto changed the title cache: add support for zstd --adapt cache: unlock zstd long mode and add support for zstd --adapt Mar 26, 2025
@smorimoto smorimoto requested review from a team as code owners March 26, 2025 06:12
@smorimoto
Copy link
Contributor Author

Gentle ping @robherley

@smorimoto
Copy link
Contributor Author

Can you review this? @salmanmkc

@joshmgross
Copy link
Contributor

@smorimoto please stop pinging GitHub Staff on this issue:

Contacting any member of GitHub Staff via unsolicited mentions or pings, or via channels other than GitHub Community itself, or the Support contact form is strongly discouraged and may be considered a violation of our prohibition against harassment.

https://docs.github.com/site-policy/github-terms/github-community-code-of-conduct#contacting-github-staff

My previous response still applies - we don't have capacity at the moment to validate, test, and rollout this change.

@smorimoto
Copy link
Contributor Author

I really don’t want to mention anyone else either, but it seems the GitHub Actions team has been struggling with triage for several years now.
It’s disappointing to see a high-impact PR like this being left unattended.
I believe the Toolkit in particular requires quite a lot of maintenance, much of which has unfortunately been left untouched.
Please forward my message to the Actions team lead.

@joshmgross
Copy link
Contributor

@smorimoto I understand your disappointment, but pinging random GitHub Staff on pull requests is not the solution.

Your feedback is appreciated though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants
0