-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Code Deploy - Unhandled exception - ZIP does not support timestamps before 1980 #2639
Comments
Same error for:
even after downgrading to |
It sounds like you have some files with invalid timestamps. This could be indicative of a larger issue, so I would recommend fixing them. Changing your version of the CLI won't impact this because the the error is raised in python itself. |
I'm noticing the exact same error message with CircleCI today, during the create_application_revision command:
|
There's also a Bug Report open on CircleCI's support forums about this. |
@JordonPhillips thanks for the quick feedback. We'll wait to see if anyone gets back to us on the CircleCi issue. @arsenio -just to note we deployed manually via code deploy directly and this solved the problem in the short term. |
So for me
|
This is happening for us too; since Sunday on our Shippable build server and locally after a
This is a nodejs app, EB CLI 3.9.0 (Python 2.7.1) Update: Looks like this is being caused by uglify-js as @mgibas says. |
@mgibas with the save: certain (but not all) files in the |
Actually seems to me to be a prob with Webpack's NPM package. Posted issue webpack/webpack#5022 |
Yeah, seems like uglify is a pretty common dependency :) |
@sumothecat it's not Webpack's issue. It's an issue with UglifyJS which webpack uses. The community needs to point fingers in the correct location as has been linked by @mgibas |
@eric-tucker we don't use Uglify, but Webpack has an implicit dependency on it. I've closed the issue in Webpack and will be using a yarn lock file in future! |
For my application, both As I already use
which let me work around this issue temporarily. |
Looking at mgibas answer, temp solution that worked for me for now after a yarn install or npm install is.
|
More robust hack to add to your {
"scripts": {
"install": "find ./node_modules/* -mtime +10950 -exec touch {} \\;"
}
} This will |
Also appears to be an issue with the |
seeing the same issues, cause by @slack/client npm this time. |
Though there is definitely an issue with some timestamps getting mangled, I don't see why this CLI tool should care. What is the reason for invalid timestamps causing this issue? Is there a way they can be supported to entirely avoid this issue? |
I had the same issue. I tried everything, but only restarting my laptop did the trick. |
Same issue and it's not an |
as suggested above i just ran |
|
This has been a recurrent issue on multiple proyects with different dependencies. |
I still run into this issue. |
Just had this issue too when I added nyc (istanbul) as a dev dependency, it looks like it added uglify-js which is the root cause of this issue. |
From my PoV, it seems related to |
We use |
Sadly, I depend on a few packages in production which cause this issue so That said, |
What is the windows command for find ./node_modules/* -mtime +10950 -exec touch {} \; I can't run this on my computer |
CodeBuild was giving me an error like: > [Container] 2020/09/21 18:50:44 Entering phase BUILD > [Container] 2020/09/21 18:50:44 Running command aws cloudformation > package --template template.yml --s3-bucket $S3_BUCKET --output-template \ > template-export.yml > Unable to upload artifact None referenced by CodeUri parameter of > HelloWorld resource. > ZIP does not support timestamps before 1980 This implements [a workaround](aws/aws-cli#2639 (comment)), slightly adapted. The command find node_modules/ -mtime +14600 -print revealed that some files within node_modules/@babel and node_modules/babel-preset-current-node-syntax were very old.
Similar to aws/aws-cli#2639
It looks like this could have been fixed by using the |
Overview
When running a deployment via circle-ci we've recently been getting the following error when running the
create_application_revision
command:I couldn't find an existing issue with the repo. We haven't changed any configuration recently. This appears to have only started happening since yesterday, it was the first time we had the error on our builds.
We're running the following versions:
If anyone is able to point us in the right direction that would be greatly appreciated.
The text was updated successfully, but these errors were encountered: