Skip to content
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

AWS assets broken #33492

Closed
Geoffmoss77 opened this issue Feb 18, 2025 · 11 comments
Closed

AWS assets broken #33492

Geoffmoss77 opened this issue Feb 18, 2025 · 11 comments
Labels
@aws-cdk/assets Related to the @aws-cdk/assets package @aws-cdk/core Related to core CDK functionality effort/medium Medium work item – several days of effort p1

Comments

@Geoffmoss77
Copy link

Hi looks like you need to replace @latest with @2 Thanks

@leantorres73
Copy link

Yes, related to #33491

All CodePipelines generated with AWS CDK are failing. :(

@klakpin
Copy link

klakpin commented Feb 18, 2025

@2 was replaced with @latest couple of month ago #31253, now CDK is broken. Anyone has a workaround?

@jeffreymrussell
Copy link

Seems to be fixed now.

@pahud
Copy link
Contributor

pahud commented Feb 18, 2025

This should have been fixed. Let me know if the issue still exists.

@pahud pahud added p1 @aws-cdk/core Related to core CDK functionality @aws-cdk/assets Related to the @aws-cdk/assets package effort/medium Medium work item – several days of effort response-requested Waiting on additional info and feedback. Will move to "closing-soon" in 7 days. labels Feb 18, 2025
@edmiester777
Copy link

I believe there is an additional issue is coming from the new version of 2.1000.0

In my case, I have a self-mutating pipeline that is broken because it is using aws/codebuild/standard:6.0 which still uses node 16 and fails with the following:

    var wasmModule = new WebAssembly.Module(bytes);
                     ^

CompileError: WebAssembly.Module(): invalid value type 'externref', enable with --experimental-wasm-reftypes @+139
    at ../../node_modules/cdk-from-cfn/index.js (/usr/local/share/npm-global/lib/node_modules/aws-cdk/lib/index.js:334202:22)
    at __require (/usr/local/share/npm-global/lib/node_modules/aws-cdk/lib/index.js:16:50)
    at lib/commands/migrate.ts (/usr/local/share/npm-global/lib/node_modules/aws-cdk/lib/index.js:336442:28)
    at __init (/usr/local/share/npm-global/lib/node_modules/aws-cdk/lib/index.js:13:56)
    at lib/cli/cdk-toolkit.ts (/usr/local/share/npm-global/lib/node_modules/aws-cdk/lib/index.js:337442:5)
    at __init (/usr/local/share/npm-global/lib/node_modules/aws-cdk/lib/index.js:13:56)
    at lib/cli/cli.ts (/usr/local/share/npm-global/lib/node_modules/aws-cdk/lib/index.js:345803:5)
    at __init (/usr/local/share/npm-global/lib/node_modules/aws-cdk/lib/index.js:13:56)
    at Object.<anonymous> (/usr/local/share/npm-global/lib/node_modules/aws-cdk/lib/index.js:346028:14)
    at Module._compile (node:internal/modules/cjs/loader:1198:14)

See the following line that installs new version that breaks this image:

`npm install -g aws-cdk${installSuffix}`,

Let me know if I'm incorrect in this assumption

@jonnysmith1981
Copy link

jonnysmith1981 commented Feb 18, 2025

To confirm that I saw the above WebAssembly error on 1.0.17 and 1.2.0 of the standard CDKDeploy step.

/usr/local/npm/lib/node_modules/aws-cdk/lib/index.js:334202
var wasmModule = new WebAssembly.Module(bytes);
^

CompileError: WebAssembly.Module(): invalid value type 'externref', enable with --experimental-wasm-reftypes @+139
at ../../node_modules/cdk-from-cfn/index.js (/usr/local/npm/lib/node_modules/aws-cdk/lib/index.js:334202:22)
at __require (/usr/local/npm/lib/node_modules/aws-cdk/lib/index.js:16:50)
at lib/commands/migrate.ts (/usr/local/npm/lib/node_modules/aws-cdk/lib/index.js:336442:28)
at __init (/usr/local/npm/lib/node_modules/aws-cdk/lib/index.js:13:56)
at lib/cli/cdk-toolkit.ts (/usr/local/npm/lib/node_modules/aws-cdk/lib/index.js:337442:5)
at __init (/usr/local/npm/lib/node_modules/aws-cdk/lib/index.js:13:56)
at lib/cli/cli.ts (/usr/local/npm/lib/node_modules/aws-cdk/lib/index.js:345803:5)
at __init (/usr/local/npm/lib/node_modules/aws-cdk/lib/index.js:13:56)
at Object.<anonymous> (/usr/local/npm/lib/node_modules/aws-cdk/lib/index.js:346028:14)
at Module._compile (node:internal/modules/cjs/loader:1198:14)

@github-actions github-actions bot removed the response-requested Waiting on additional info and feedback. Will move to "closing-soon" in 7 days. label Feb 18, 2025
@edmiester777
Copy link

@jonnysmith1981 issue referenced in #33494

@andreprawira
Copy link

@jonnysmith1981 We started getting the same exact error today when we run the code in our codepipeline. Note that when we cdk ls and synth locally, we dont see the error. Then we updated CDK to version 2.175.1, changed python3 to python in our cdk.json and then we passed through that and got to this error which is also opened today #33495

Before that (but also today) we got error in FileAsset stage related to NPM which suddenly fixed on its own. Seems AWS released something on their end that broke some components?

@edmiester777
Copy link

@jonnysmith1981 We started getting the same exact error today when we run the code in our codepipeline. Note that when we cdk ls and synth locally, we dont see the error. Then we updated CDK to version 2.175.1, changed python3 to python in our cdk.json and then we passed through that and got to this error which is also opened today #33495

Before that (but also today) we got error in FileAsset stage related to NPM which suddenly fixed on its own. Seems AWS released something on their end that broke some components?

lolol yeah I'm now seeing this with 2.1000.1. Looks like they sorted out the wasm one, but this is new. At this point they should just rollback to 2.179.0 because almost everyone is completely unable to deploy stuff at the moment.

Seems like the version split should have happened after significantly more testing.

@rix0rrr
Copy link
Contributor

rix0rrr commented Feb 18, 2025

If you are seeing Invalid URL and you can help us figure out what's causing it, please join #33495 and let us know.

The cdk-assets and WASM issues have been resolved, closing this.

@rix0rrr rix0rrr closed this as completed Feb 18, 2025
Copy link

Comments on closed issues and PRs are hard for our team to see.
If you need help, please open a new issue that references this one.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 18, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
@aws-cdk/assets Related to the @aws-cdk/assets package @aws-cdk/core Related to core CDK functionality effort/medium Medium work item – several days of effort p1
Projects
None yet
Development

No branches or pull requests

9 participants