-
-
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
Research about actions/upload-artifact@v4 and actions/download-artifact@v4 #2135
Comments
Hmm they are not using protobuf in the toolkit yet, but the code exists They use the json representation of protobuf and not the binary protocol. |
Only the origin of Base url is always
GHES and GITEA are blocked by the current toolkit code and won't work as of now. Gitea would have to switch to jwt tokens if they would want to support artifacts v4 from GitHub as soon it is allowed in GHES |
@ChristopherHX what's the current state of When using new version, I'm getting
which is consistent with your findings about jwt tokens above. |
0% in gitea 80%, it's also in go so not that much to fear. We could port go-gitea/gitea@main...ChristopherHX:gitea:gitea-artifacts-v4 to act. My time is currently limited due to exam period. ACTIONS_RUNTIME_TOKEN has never been set by act itself... |
- Issue: nektos/act#329 - Discussion: nektos/act#2135
I'm still getting |
Also seeing this with |
The fix is #2224, but it doesn't meet the 50% (has 40%) coverage requirement of this project. Due to unused generated code of google protobuf. go-gitea/gitea requirements are not that strict and it has been merged months ago |
@ChristopherHX thanks for your work on this, and for the update. |
I think I've hit the same issue on act version 0.2.62:
This workflow works fine on github. |
Hi @ChristopherHX. Thanks very much for the note about the JWT token to fix the problem with However, running on e1e5671 I'm getting a related error: I'm invoking
(That jwt has the contents you suggested, see jwt.io). Apologies if I've missed something here. Let me know if I should file a new issue or specify an ACTIONS_RESULTS_URL in the environment. Extract from output:
|
I don't know what you are doing..... this is missing a dash (-)
And doing For me it works like that
|
Also if |
Thanks very much for your response, @ChristopherHX . Apologies, the missing hyphen was the problem. I can confirm that
runs successfully from a fresh compilation from e1e5671 and from the latest artifact run on linux amd64. For anyone needing a jwt, please see the comment concerning making jwt with the contents
for example this one. |
With the PR merged, do we still need to manually mint a JWT? Shouldn't act be doing that internally? |
You are right, @TWiStErRob
Apologies for the noise. |
sorry is there any release ETA? |
I didn't even create this as a feature request, this issue contains much technical details for implementing the feature from scratch. Therefore are references to the jwt format or the google protobuf file part of this issue, all of them are mostly irrelevant for users of the act executable.
Nobody prevents you from downloading the executable associated with all Pullrequests that are merged from the GitHub Artifact List or just clone or doing a |
Decompiled proto for artifacts from toolkit only typescript sources provided by GitHub.
Source
Notice, this was decompiled by bing chatbot and only required include fixes
You can do it yourself using that prompt and place classes as long they don't hit the content length. I have converted multiple times to get the final list of all Messages.
Update 2024-02-17: Delete Artifact Endpoint proto
The text was updated successfully, but these errors were encountered: