dan-hook

> Hey @dan-hook 👋 what is the use case for a Lambda invoking itself? A lambda can take a single work item, or a list. The first invocation is given...

> We have encountered the same issue and the function parameters.json changes make us fairly distressed. Using the example above: > > ``` > { > "lambdaLayers": [ > {...

@bothra90 > "VpcConfig": { > "SecuritGroupIds": { > "Ref": "securityGroupIds" > }, Typo in "SecuritGroupIds"

> Hey @dan-hook 👋 thanks for raising this! Was the `amplify/mock-data` directory deleted before mock finished initializing? Looking at this log item: > > ``` > Mock DB deletion detected....

My best guess is that this bug was introduced [in this PR](https://github.com/pypa/pipenv/pull/6029/files#diff-3773f79ed29343c21d129b164b9c100379ff04acca7245712bdded50fd43e70cL79-R81).

I've never used `--all-dev`, but I recall seeing the same strange behavior [in the docs](https://pipenv.pypa.io/en/latest/commands.html#uninstall:~:text=%2D%20%2D%2Dall%20%E2%80%94%20This%20parameter%20will%20purge%20all%20files%20from%20the%20virtual%20environment%2C%0A%20%20but%20leave%20the%20Pipfile%20untouched.%0A%0A%2D%20%2D%2Dall%2Ddev%20%E2%80%94%20This%20parameter%20will%20remove%20all%20of%20the%20development%20packages%20from%0A%20%20the%20virtual%20environment%2C%20and%20remove%20them%20from%20the%20Pipfile.). Since a change in `--all` behavior broke my workflow, I'd be sympathetic to anyone who...

I've been adding (or deleting) empty lines in my lambda sources files to work around this.