‼️ NOTICE: 'Error: ENOTDIR invalid cwd' on `cdk deploy` in 1.90.0 #13131

qs-wang · 2021-02-18T07:22:57Z

Please add your +1 👍 to let us know you have encountered this

Update

Version 1.90.1 which includes a fix is now released.

There is an issue with the way the CDK assets mechanism identifies already .zip file. Currently it will try to zip the already zipped file that will throw an error. We are working on a fix.

Workaround

TL;DR: delete the cdk.out folder before executing cdk deploy

The issue occurs when executing cdk deploy when there is a .zip file in the cdk.out folder. This happens when executing cdk synth - which creates the cdk.out folder, followed by cdk deploy (which is a completely normal cdk flow). To workaround this, delete the cdk.out folder before executing cdk deploy.

Repro

Any application which includes an asset with a .zip file will fail to deploy:

new lambda.Function(this, 'MyLambda', {
      code: lambda.Code.fromAsset(path.join(__dirname, '../my-zip.zip')),
      handler: 'index.handler',
      runtime: lambda.Runtime.NODEJS_12_X
 })

important: execute cdk synth before executing cdk deploy

cdk deploy will throw:

UnhandledPromiseRejectionWarning: Error: ENOTDIR invalid cwd

Status: Working on a patch release

Overview:

When running cdk deploy in version 1.90.0 on a Stack that contains assets, you might see an error like 'Error: ENOTDIR invalid cwd.

Complete Error Message:

$ npx cdk deploy --require-approval=never 
Bug13131Stack: deploying...
[0%] start: Publishing e9882ab123687399f934da0d45effe675ecc8ce13b40cb946f3e1d6141fe8d68:current
(node:81012) UnhandledPromiseRejectionWarning: Error: ENOTDIR invalid cwd /Users/adamruka/workplace/cdk/on-call/bug-13131/cdk.out/asset.e9882ab123687399f934da0d45effe675ecc8ce13b40cb946f3e1d6141fe8d68.zip
    at GlobSync._readdirError (/Users/adamruka/workplace/cdk/on-call/bug-13131/node_modules/aws-cdk/node_modules/glob/sync.js:324:21)
    at GlobSync._readdir (/Users/adamruka/workplace/cdk/on-call/bug-13131/node_modules/aws-cdk/node_modules/glob/sync.js:290:10)
    at GlobSync._processGlobStar (/Users/adamruka/workplace/cdk/on-call/bug-13131/node_modules/aws-cdk/node_modules/glob/sync.js:350:22)
    at GlobSync._process (/Users/adamruka/workplace/cdk/on-call/bug-13131/node_modules/aws-cdk/node_modules/glob/sync.js:130:10)
    at new GlobSync (/Users/adamruka/workplace/cdk/on-call/bug-13131/node_modules/aws-cdk/node_modules/glob/sync.js:48:10)
    at Function.globSync [as sync] (/Users/adamruka/workplace/cdk/on-call/bug-13131/node_modules/aws-cdk/node_modules/glob/sync.js:26:10)
    at Promise (/Users/adamruka/workplace/cdk/on-call/bug-13131/node_modules/aws-cdk/node_modules/cdk-assets/lib/private/archive.ts:17:24)
    at new Promise (<anonymous>)
    at Object.zipDirectory (/Users/adamruka/workplace/cdk/on-call/bug-13131/node_modules/aws-cdk/node_modules/cdk-assets/lib/private/archive.ts:7:10)
    at FileAssetHandler.packageFile (/Users/adamruka/workplace/cdk/on-call/bug-13131/node_modules/aws-cdk/node_modules/cdk-assets/lib/private/handlers/files.ts:78:13)
(node:81012) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2)
(node:81012) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Original bug report

My CDK script was all right, but was failing with the latest 1.90.0 version

Reproduction Steps

Run the CDK script via gitlab pipeline

What did you expect to happen?

No errors

What actually happened?

See the error message as below:

xxxx- infra-Dev: deploying...
[0%] start: Publishing 45f6bfc57a7695260616f2916fbef2dd77200af18743d956a59c8db9c3816b3f:current
(node:55) UnhandledPromiseRejectionWarning: Error: ENOTDIR invalid cwd /builds/xxxx/cdk.out/asset.45f6bfc57a7695260616f2916fbef2dd77200af18743d956a59c8db9c3816b3f.sh
    at GlobSync._readdirError (/usr/local/lib/node_modules/aws-cdk/node_modules/glob/sync.js:324:21)
    at GlobSync._readdir (/usr/local/lib/node_modules/aws-cdk/node_modules/glob/sync.js:290:10)
    at GlobSync._processGlobStar (/usr/local/lib/node_modules/aws-cdk/node_modules/glob/sync.js:350:22)
    at GlobSync._process (/usr/local/lib/node_modules/aws-cdk/node_modules/glob/sync.js:130:10)
    at new GlobSync (/usr/local/lib/node_modules/aws-cdk/node_modules/glob/sync.js:48:10)
    at Function.globSync [as sync] (/usr/local/lib/node_modules/aws-cdk/node_modules/glob/sync.js:26:10)
    at /usr/local/lib/node_modules/aws-cdk/node_modules/cdk-assets/lib/private/archive.ts:17:24
    at new Promise (<anonymous>)
    at Object.zipDirectory (/usr/local/lib/node_modules/aws-cdk/node_modules/cdk-assets/lib/private/archive.ts:7:10)
    at FileAssetHandler.packageFile (/usr/local/lib/node_modules/aws-cdk/node_modules/cdk-assets/lib/private/handlers/files.ts:78:13)
(node:55) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)
(node:55) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Environment

CDK CLI Version : 1.90.0
**Framework Version: **1.90.0
**Node.js Version: **12
OS : Docker
Language (Version): Python (3.8)

Other

Rollback to 1.89.0 fixed the problem

This is 🐛 Bug Report

The text was updated successfully, but these errors were encountered:

mohdwasee · 2021-02-18T14:02:10Z

Facing same issue with me as well

morgler · 2021-02-18T16:56:34Z

I get the same error when trying to deploy a simple static website:

const deployment = new s3deploy.BucketDeployment(this, 'DeployFrontend', {
      sources: [s3deploy.Source.asset('./frontend/dist')],
      destinationBucket: siteBucket,
      distribution,
      distributionPaths: ['/*']
    })

Version is also 1.90.0. Everything works when downgrading to 1.89.0.

bigkraig · 2021-02-18T18:10:16Z

I've noticed the same problem when using a BucketDeployment. The zip exists at the path and contains awscli.

Do you wish to deploy these changes (y/n)? y
cwf-kraig-f9aca73e: deploying...
[0%] start: Publishing e9882ab123687399f934da0d45effe675ecc8ce13b40cb946f3e1d6141fe8d68:739368017290-us-west-2

/Users/kamador/src/service/sysops/cdk/node_modules/glob/sync.js:324
        var error = new Error(er.code + ' invalid cwd ' + this.cwd)
                    ^
Error: ENOTDIR invalid cwd /Users/kamador/src/service/sysops/cdk/cdk.out/asset.e9882ab123687399f934da0d45effe675ecc8ce13b40cb946f3e1d6141fe8d68.zip
    at GlobSync._readdirError (/Users/kamador/src/service/sysops/cdk/node_modules/glob/sync.js:324:21)
    at GlobSync._readdir (/Users/kamador/src/service/sysops/cdk/node_modules/glob/sync.js:290:10)
    at GlobSync._processGlobStar (/Users/kamador/src/service/sysops/cdk/node_modules/glob/sync.js:350:22)
    at GlobSync._process (/Users/kamador/src/service/sysops/cdk/node_modules/glob/sync.js:130:10)
    at new GlobSync (/Users/kamador/src/service/sysops/cdk/node_modules/glob/sync.js:48:10)
    at Function.globSync [as sync] (/Users/kamador/src/service/sysops/cdk/node_modules/glob/sync.js:26:10)
    at /Users/kamador/src/service/sysops/cdk/node_modules/cdk-assets/lib/private/archive.ts:17:24
    at new Promise (<anonymous>)
    at Object.zipDirectory (/Users/kamador/src/service/sysops/cdk/node_modules/cdk-assets/lib/private/archive.ts:7:10)
    at FileAssetHandler.packageFile (/Users/kamador/src/service/sysops/cdk/node_modules/cdk-assets/lib/private/handlers/files.ts:78:13)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

skinny85 · 2021-02-18T18:26:57Z

Confirming I was able to reproduce this. We're working on a fix.

michaelbrewer · 2021-02-18T21:57:12Z

Are we missing some test cases to prevent this from happening again?

NetaNir · 2021-02-18T22:03:51Z

If everyone (or some) who are seeing this issue can comment with the node version they are using, it will help us debug it. Thanks!

mark-ship-it · 2021-02-18T22:20:18Z

I am using node v14.15.0

AjkayAlan · 2021-02-18T22:36:18Z

Node v14.15.5 for us, which is the latest default node version on GitHub Actions Linux Agents and Azure DevOps Linux Agents (per https://github.com/actions/virtual-environments/blob/main/images/linux/Ubuntu2004-README.md).

w601sxs · 2021-02-18T23:00:58Z

Help! Using Cloud9 to deploy this stack fails https://github.com/aws-samples/faropt

worked until last week and have tested in few regions now

Node v10.23.3
CDK 1.89.0 (build df7253c)

Trace is

Do you wish to deploy these changes (y/n)? y
faropt: deploying...
[0%] start: Publishing 4b6bf88ce4fd3e5943d206b3300f8d5846e09675d09aae093934d92df866158c:current
[16%] success: Published 4b6bf88ce4fd3e5943d206b3300f8d5846e09675d09aae093934d92df866158c:current
[16%] start: Publishing 8c227cb226e60cc02fb88f016ad06f18182fae243c2aac8a27e023431583d22a:current
(node:6971) UnhandledPromiseRejectionWarning: Error: ENOTDIR invalid cwd /home/ec2-user/environment/faropt/cdk.out/asset.8c227cb226e60cc02fb88f016ad06f18182fae243c2aac8a27e023431583d22a.zip
at GlobSync._readdirError (/home/ec2-user/.nvm/versions/node/v10.23.3/lib/node_modules/cdk/node_modules/aws-cdk/node_modules/glob/sync.js:324:21)
at GlobSync._readdir (/home/ec2-user/.nvm/versions/node/v10.23.3/lib/node_modules/cdk/node_modules/aws-cdk/node_modules/glob/sync.js:290:10)
at GlobSync._processGlobStar (/home/ec2-user/.nvm/versions/node/v10.23.3/lib/node_modules/cdk/node_modules/aws-cdk/node_modules/glob/sync.js:350:22)
at GlobSync._process (/home/ec2-user/.nvm/versions/node/v10.23.3/lib/node_modules/cdk/node_modules/aws-cdk/node_modules/glob/sync.js:130:10)
at new GlobSync (/home/ec2-user/.nvm/versions/node/v10.23.3/lib/node_modules/cdk/node_modules/aws-cdk/node_modules/glob/sync.js:48:10)
at Function.globSync [as sync] (/home/ec2-user/.nvm/versions/node/v10.23.3/lib/node_modules/cdk/node_modules/aws-cdk/node_modules/glob/sync.js:26:10)
at Promise (/home/ec2-user/.nvm/versions/node/v10.23.3/lib/node_modules/cdk/node_modules/aws-cdk/node_modules/cdk-assets/lib/private/archive.ts:17:24)
at new Promise ()
at Object.zipDirectory (/home/ec2-user/.nvm/versions/node/v10.23.3/lib/node_modules/cdk/node_modules/aws-cdk/node_modules/cdk-assets/lib/private/archive.ts:7:10)
at FileAssetHandler.packageFile (/home/ec2-user/.nvm/versions/node/v10.23.3/lib/node_modules/cdk/node_modules/aws-cdk/node_modules/cdk-assets/lib/private/handlers/files.ts:78:13)
(node:6971) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 4)
(node:6971) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

NetaNir · 2021-02-18T23:02:25Z

@w601sxs an you verify the CDK version? and that you are not using 1.90, which we suspect have the bug?

bigkraig · 2021-02-18T23:08:27Z

im using v15.8.0, after also seeing this problem with a brew installed node v14

NetaNir · 2021-02-18T23:18:46Z

@bigkraig which CDK version?

bigkraig · 2021-02-18T23:24:16Z

my bad, 1.90.0

NetaNir · 2021-02-18T23:28:39Z

@bigkraig would you mind verifying that it works with 1.89? I suspect it will not, and the problem is actually in one of our transient dependencies

bigkraig · 2021-02-19T00:06:17Z

@NetaNir i actually had tried to do that right away but ran into a NPM dependency nightmare that i ultimately didn't have time to keep beating my head against, vowing to wait until this PR was resolved. i'll see if i can get some time to look at this again but it might not be until my lunch tomorrow.

mark-ship-it · 2021-02-19T00:10:12Z

@NetaNir , I can confirm my deployment worked with 1.89

NetaNir · 2021-02-19T01:24:27Z

Possibly related: #12536

ccaaau · 2021-02-19T02:10:25Z

I think @NetaNir is right that it has something to do with dependencies.

Notes:

Wont allow upgrade from 1.89 to 1.90
Modifies dependencies so that @aws-cdk/aws-ec2 is 1.90 but others are 1.89 - almost as if it stops updating dependencies there
Will generate all sorts of compatibility errors including type errors
Affects not only parent project but its module folders (makes it complicated to cleanup)
Delete of node modules folder will require a clear of cache
Breaks after issuing update command multiple times (works only first time)
Even if resolved in project scope will generate an error because chances are global installs of modules need to be resolved also
Even after conflicts are resolved it will error as @bigkraig noted

Also note some import conflicts may start to occur on existing code between:

@aws-cdk/core and @aws-cdk/aws-iam
@aws-cdk/core and @aws-cdk/aws-ec2

Not sure if any of the above helps but if it does then Kudos!

cod3monk3y · 2021-02-19T02:54:19Z

@bigkraig would you mind verifying that it works with 1.89? I suspect it will not, and the problem is actually in one of our transient dependencies

I'm seeing the error with:

node v14.15.5
cdk 1.89.0 (build df7253c)

(node:24672) UnhandledPromiseRejectionWarning: Error: ENOTDIR invalid cwd E:\path-to-project\cdk.out\asset.xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.zip

NetaNir · 2021-02-19T02:57:13Z

cdk 1.89.0

Can you verify that this is in fact the version of the CDK CLI (aws-cdk) used? cdk --version. All reports we have seen so far only see the problem in version 1.90.0

cod3monk3y · 2021-02-19T02:59:25Z

cdk 1.89.0

Can you verify that this is in fact the version of the CDK CLI (aws-cdk) used? cdk --version. All reports we have seen so far only see the problem in version 1.90.0

Yes, that is how I got the version numbers.

(.venv) ...>node --version
v14.15.5

(.venv) ...>cdk --version
1.89.0 (build df7253c)

ccaaau · 2021-02-19T03:33:17Z

Updating package configuration from:

"@aws-cdk/aws-ec2": "^1.89.0",
"@aws-cdk/aws-elasticbeanstalk": "^1.89.0",
"@aws-cdk/aws-s3-assets": "^1.89.0",

to

"@aws-cdk/aws-ec2": "1.89.0",
"@aws-cdk/aws-elasticbeanstalk": "1.89.0",
"@aws-cdk/aws-s3-assets": "1.89.0",

Fixed the problem for me. I'm not sure which is the culprit but I suspect it is the EC2 module (see my previous comment above). Using the ^ (Compatible with version) seems to have something to do with it. Has to be specifically 1.89.0 - though I have not tried this fix with 1.90.0...

michaelbrewer · 2021-02-19T04:25:41Z

Are we missing some test cases to prevent this from happening again?

For me it was:

node: v12.20.2
cdk: 1.90.0
stacks written in kotlin on 1.90.0

Otherwise, would there be a version that does not rely on node being installed? And can the cdk team include real end to end test cases deploying to a dummy aws account for stable releases?

NetaNir · 2021-02-19T05:03:44Z

Thanks everyone, we found the problem and we are working on a fix. The problem was introduced in version 1.90.0 and affect all node version. We are on it

This commit reverts two recent changes to the asset system (#12258 and ##13076) which introduced a regression in 1.90.0. Fixes #13131

eladb · 2021-02-19T07:15:20Z

Revert #13145

This commit reverts two recent changes to the asset system (#12258 and ##13076) which introduced a regression in 1.90.0. Fixes #13131 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*

github-actions · 2021-02-19T08:17:34Z

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

NetaNir · 2021-02-19T08:34:18Z

Added a workaround to the issue description, TL;DR: delete the cdk.out folder before executing cdk deploy.

A patch is on the way!

This commit reverts two recent changes to the asset system (#12258 and ##13076) which introduced a regression in 1.90.0. Fixes #13131 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*

jogold · 2021-02-19T09:12:40Z

@NetaNir @eladb found the bug and running synth two times will also reproduce it.

After the first synth the packaging is correctly set to file in the manifest.json. But then the asset cache comes into play and the second time it runs packaging is now set to zip in the manifest.json.

This is because staging doesn't rerun:

aws-cdk/packages/@aws-cdk/core/lib/asset-staging.ts

Line 191 in cd7a3ed

const staged = AssetStaging.assetCache.obtain(this.cacheKey, stageThisAsset);

and the FileAssetPackaging is set in the staging private methods not in the constructor.

On it for a redo.

This is only #13076.

eladb · 2021-02-19T09:22:55Z

Thanks @jogold. No rush. We reverted the other commit just because there were some merge conflicts.

w601sxs · 2021-02-19T18:50:26Z

@w601sxs an you verify the CDK version? and that you are not using 1.90, which we suspect have the bug?

Yes, I can confirm it's 1.89

And I can confirm that deleting the cdk.out directory works for 1.89 as well

baumannalexj · 2021-02-19T21:16:06Z

If everyone (or some) who are seeing this issue can comment with the node version they are using, it will help us debug it. Thanks!

node v12.20.1

github-actions · 2021-02-20T00:15:24Z

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

This commit reverts two recent changes to the asset system (#12258 and ##13076) which introduced a regression in 1.90.0. Fixes #13131 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*

Redo of #13076 after #13131. The fix is [`7b3d829` (#13152)](7b3d829). If the bundling output contains a single archive file (zip or jar), upload it as-is to S3 without zipping it. Allow to customize this behavior with `bundling.outputType`: * `NOT_ARCHIVED`: The bundling output will always be zipped and uploaded to S3. * `ARCHIVED`: The bundling output will not be zipped. Bundling will fail if the bundling output doesn't contain a single archive file. * `AUTO_DISCOVER`: If the bundling output contains a single archive file (zip or jar) it will not be zipped. Otherwise it will be zipped. This is the default. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*

pandrel · 2021-03-02T16:55:19Z

Deleting cdk.out directory did not work

❯ node --version
v15.5.0

cdk and module versions

├── @aws-cdk/assert@1.90.1
├── @aws-cdk/aws-dynamodb@1.90.1
├── @aws-cdk/aws-ec2@1.90.1
├── @aws-cdk/aws-glue@1.90.1
├── @aws-cdk/aws-lambda@1.90.1
├── @aws-cdk/aws-redshift@1.90.1
├── @aws-cdk/aws-s3-deployment@1.90.1
├── @aws-cdk/aws-s3@1.90.1
├── @aws-cdk/aws-secretsmanager@1.90.1
├── @aws-cdk/aws-ssm@1.90.1
├── @aws-cdk/aws-stepfunctions-tasks@1.90.1
├── @aws-cdk/aws-stepfunctions@1.90.1
├── @aws-cdk/core@1.90.1
├── @types/jest@26.0.20
├── @types/node@10.17.27
├── aws-cdk@1.90.1
├── jest@26.6.3
├── source-map-support@0.5.19
├── ts-jest@26.5.2
├── ts-node@9.1.1
└── typescript@3.9.9

qs-wang added bug This issue is a bug. needs-triage This issue or PR still needs to be triaged. labels Feb 18, 2021

skinny85 added p0 and removed needs-triage This issue or PR still needs to be triaged. labels Feb 18, 2021

skinny85 changed the title ~~1.90 failed the working script~~ ‼️ NOTICE: 'Error: ENOTDIR invalid cwd' on cdk deploy Feb 18, 2021

skinny85 self-assigned this Feb 18, 2021

skinny85 added the management/tracking Issues that track a subject or multiple issues label Feb 18, 2021

skinny85 pinned this issue Feb 18, 2021

skinny85 changed the title ~~‼️ NOTICE: 'Error: ENOTDIR invalid cwd' on cdk deploy~~ ‼️ NOTICE: 'Error: ENOTDIR invalid cwd' on cdk deploy in 1.90.0 Feb 18, 2021

NetaNir mentioned this issue Feb 19, 2021

feat(core): customize bundling output packaging #13076

Merged

NetaNir assigned NetaNir and unassigned skinny85 Feb 19, 2021

eladb pushed a commit that referenced this issue Feb 19, 2021

fix: ENOTDIR invalid cwd on "cdk deploy"

4f02b45

This commit reverts two recent changes to the asset system (#12258 and ##13076) which introduced a regression in 1.90.0. Fixes #13131

eladb pushed a commit that referenced this issue Feb 19, 2021

fix: ENOTDIR invalid cwd on "cdk deploy"

40b7932

This commit reverts two recent changes to the asset system (#12258 and ##13076) which introduced a regression in 1.90.0. Fixes #13131

eladb mentioned this issue Feb 19, 2021

fix(core): ENOTDIR invalid cwd on "cdk deploy" #13145

Merged

mergify bot closed this as completed in #13145 Feb 19, 2021

NetaNir reopened this Feb 19, 2021

NetaNir linked a pull request Feb 19, 2021 that will close this issue

chore(release): 1.90.1 #13148

Merged

jogold mentioned this issue Feb 19, 2021

feat(core): customize bundling output packaging #13152

Merged

NetaNir closed this as completed Feb 20, 2021

rix0rrr unpinned this issue Mar 17, 2021

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

‼️ NOTICE: 'Error: ENOTDIR invalid cwd' on `cdk deploy` in 1.90.0 #13131

‼️ NOTICE: 'Error: ENOTDIR invalid cwd' on `cdk deploy` in 1.90.0 #13131

qs-wang commented Feb 18, 2021 •

edited by NetaNir

Loading

mohdwasee commented Feb 18, 2021

morgler commented Feb 18, 2021 •

edited

Loading

bigkraig commented Feb 18, 2021

skinny85 commented Feb 18, 2021

michaelbrewer commented Feb 18, 2021

NetaNir commented Feb 18, 2021

mark-ship-it commented Feb 18, 2021

AjkayAlan commented Feb 18, 2021

w601sxs commented Feb 18, 2021

NetaNir commented Feb 18, 2021

bigkraig commented Feb 18, 2021

NetaNir commented Feb 18, 2021

bigkraig commented Feb 18, 2021

NetaNir commented Feb 18, 2021

bigkraig commented Feb 19, 2021

mark-ship-it commented Feb 19, 2021

NetaNir commented Feb 19, 2021 •

edited

Loading

ccaaau commented Feb 19, 2021 •

edited

Loading

cod3monk3y commented Feb 19, 2021 •

edited

Loading

NetaNir commented Feb 19, 2021

cod3monk3y commented Feb 19, 2021

ccaaau commented Feb 19, 2021 •

edited

Loading

michaelbrewer commented Feb 19, 2021

NetaNir commented Feb 19, 2021

eladb commented Feb 19, 2021

github-actions bot commented Feb 19, 2021

NetaNir commented Feb 19, 2021

jogold commented Feb 19, 2021 •

edited

Loading

eladb commented Feb 19, 2021

w601sxs commented Feb 19, 2021 •

edited

Loading

baumannalexj commented Feb 19, 2021

github-actions bot commented Feb 20, 2021

pandrel commented Mar 2, 2021

‼️ NOTICE: 'Error: ENOTDIR invalid cwd' on cdk deploy in 1.90.0 #13131

‼️ NOTICE: 'Error: ENOTDIR invalid cwd' on cdk deploy in 1.90.0 #13131

Comments

qs-wang commented Feb 18, 2021 • edited by NetaNir Loading

Please add your +1 👍 to let us know you have encountered this

Update

Workaround

Repro

Status: Working on a patch release

Overview:

Complete Error Message:

Original bug report

Reproduction Steps

What did you expect to happen?

What actually happened?

Environment

Other

mohdwasee commented Feb 18, 2021

morgler commented Feb 18, 2021 • edited Loading

bigkraig commented Feb 18, 2021

skinny85 commented Feb 18, 2021

michaelbrewer commented Feb 18, 2021

NetaNir commented Feb 18, 2021

mark-ship-it commented Feb 18, 2021

AjkayAlan commented Feb 18, 2021

w601sxs commented Feb 18, 2021

NetaNir commented Feb 18, 2021

bigkraig commented Feb 18, 2021

NetaNir commented Feb 18, 2021

bigkraig commented Feb 18, 2021

NetaNir commented Feb 18, 2021

bigkraig commented Feb 19, 2021

mark-ship-it commented Feb 19, 2021

NetaNir commented Feb 19, 2021 • edited Loading

ccaaau commented Feb 19, 2021 • edited Loading

cod3monk3y commented Feb 19, 2021 • edited Loading

NetaNir commented Feb 19, 2021

cod3monk3y commented Feb 19, 2021

ccaaau commented Feb 19, 2021 • edited Loading

michaelbrewer commented Feb 19, 2021

NetaNir commented Feb 19, 2021

eladb commented Feb 19, 2021

github-actions bot commented Feb 19, 2021

⚠️COMMENT VISIBILITY WARNING⚠️

NetaNir commented Feb 19, 2021

jogold commented Feb 19, 2021 • edited Loading

eladb commented Feb 19, 2021

w601sxs commented Feb 19, 2021 • edited Loading

baumannalexj commented Feb 19, 2021

github-actions bot commented Feb 20, 2021

⚠️COMMENT VISIBILITY WARNING⚠️

pandrel commented Mar 2, 2021

‼️ NOTICE: 'Error: ENOTDIR invalid cwd' on `cdk deploy` in 1.90.0 #13131

‼️ NOTICE: 'Error: ENOTDIR invalid cwd' on `cdk deploy` in 1.90.0 #13131

qs-wang commented Feb 18, 2021 •

edited by NetaNir

Loading

morgler commented Feb 18, 2021 •

edited

Loading

NetaNir commented Feb 19, 2021 •

edited

Loading

ccaaau commented Feb 19, 2021 •

edited

Loading

cod3monk3y commented Feb 19, 2021 •

edited

Loading

ccaaau commented Feb 19, 2021 •

edited

Loading

jogold commented Feb 19, 2021 •

edited

Loading

w601sxs commented Feb 19, 2021 •

edited

Loading