Kethan sai

Hey @dkliss, noticed you were able to setup a Github Actions on https://github.com/aws-amplify/amplify-cli/issues/13661, would you require any assistance on this?

@dkliss thank you for the information. I was able to reproduce this on a Github action. I was able to get this working by using the following ```yml - name:...

@dkliss glad to hear, just a quick observation on your script it appears the Amplify CLI is being installed twice, with once with curl and once with npm.

Hey @JackDurden00, could you run `amplify diagnose --send-report` and provide us the project identifier output.

@JackDurden00 could you email us your amplify folder to `[email protected]`? this would enable us in diving deeper into the issue.

Hey @JackDurden00, thank you for information. On diving into the diagnose report, did notice the `functiontokenizer` is a lambda layer (`tokenizer`) under the function folder. Tried to reproduce the issue...

@JackDurden00 we can trigger an update on the Lambda layer by adding a package in the `package.json` in the `functions/` folder

@JackDurden00 yes if run a push with a new package do observe a error? if you still run into a error and a function does not depend Lambda layer could...

@JackDurden00 either is fine. you can run push with `--debug` before just to ensure they are no errors.

Hey @Alicewyz, thank you for reaching out. Diving into the error message this appears to be a NodeJS buffer limit. could you try setting the `max-old-space-size` to a higher value...