-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Publish the .proto files for the new cache service #1931
Comments
FWIW ChatGPT was able to reconstruct the original proto files from the generated typescript. See https://github.com/andreabedini/actions-cache-proto. |
The page you linked to is not available and leads to a 404. |
Some preliminary attempts with reconstructed protobuf: https://github.com/NickCao/github-actions-cache, it does work with the also twrip based artifact service (also noticed that you can fake a 8EB artifact for fun). |
@Luflosi sorry, I forgot to make the repo public. It should be visible now. |
I also have been using chatgpt / ms copilot for that usecase like for artifacts v4 in Dec. 2023, good to know not only I had such a idea. Now I have my experimental backend as well: ChristopherHX/runner.server#519 So far the v2 client works for me, need to test the blob uploading part. Found this issue while looking for the state of docker buildx gha cache. |
Hi,
My company has a project, Magic Nix Cache, that uses the GitHub Actions cache API to serve as a Nix binary cache in CI.
Given the new cache backend and the sunsetting of the old one, I'm looking to update a project that uses the v1 api directly. It looks like the .proto files are not checked in to this repo, and only the generated code is present.
Are these proto files intentionally excluded? If so, Magic Nix Cache is going to break suddenly and be very challenging to make work again. That would be unfortunate, because it gives Nix users a no/low-cost binary cache for small projects' CI, using just the GitHub Actions primitives.
Please consider publishing the proto files.
The text was updated successfully, but these errors were encountered: