-
-
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
Meta-copy-symlinks-new-actions-cache #2337
Conversation
🦙 MegaLinter status: ✅ SUCCESS
See detailed report in MegaLinter reports |
@jsoref Please play around with this change to the "--use-new-action-cache`.
act is my golang playground, there are bugs hiding behind every corner |
If this is in, I might propose to retire the old action cache and update all tests to use the new cache. |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #2337 +/- ##
===========================================
+ Coverage 61.56% 76.25% +14.68%
===========================================
Files 53 61 +8
Lines 9002 7803 -1199
===========================================
+ Hits 5542 5950 +408
+ Misses 3020 1297 -1723
- Partials 440 556 +116 ☔ View full report in Codecov by Sentry. |
It's relatively easy to parse the error to relating to Act yields this:
|
actually act shouldn't defer the error so much, because the error is around this line
And not at the end. |
I now have added Missing filetime from git has been oberserved by me, in https://github.com/nektos/act/tree/meta-keep-filetime I tried adding it. Not shure about the performance due to calling gogit.log here... or if it is worth adding this. |
This is definitely better:
Are you still trying to get rid of an |
And yes, I noticed the zeroed timestamps when I was comparing / trying to determine what was going wrong. But I determined it wasn't the most pressing part. |
I think this is a bug of older code. In the Finally executor seem to cause this by unconditionally including both err. The first print of the error doesn't have these text portion. |
Right. I'm not saying you have to fix it / fix it here. In the long term, can some of this be dropped:
Personally, I'd much rather much less of it -- given that the problem is purely an act / workflow thing parsing actions and has no material relation to the underlying transport (docker). |
One problem you would have to take into account is streaming the virtual tar archive. Or wrap the error into a special error type and drop the outer part of the docker library if it matches |
Experimental
Fixes #2334