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

WriteToGithub lambda throws new / different error than #2 #4

Open
weisisheng opened this issue Jan 12, 2023 · 0 comments
Open

WriteToGithub lambda throws new / different error than #2 #4

weisisheng opened this issue Jan 12, 2023 · 0 comments

Comments

@weisisheng
Copy link
Contributor

weisisheng commented Jan 12, 2023

Oddly, this issue has popped up for me and googling doesn't surface any solutions.

{
"errorType": "SyntaxError",
"errorMessage": "Unexpected end of JSON input",
"trace": [
"SyntaxError: Unexpected end of JSON input",
" at JSON.parse ()",
" at Runtime.exports.handler (/var/task/WriteToGitHub.js:14:22)",
" at Runtime.handleOnceNonStreaming (/var/runtime/Runtime.js:74:25)"
]
}


Using this as a reference-->

#2

Have tried to use with/without backslashes on both the github repo reference and the content.json reference in the SAM template.

github-repo/foo

github-repo/foo/

and

/frontend/content.json

frontend/content.json

Moreover, there is a space in the WriteToGitHub.js github key reference that I removed for my own repo. But no difference in error.

const singleParam = { Name: '/GitHubAPIKey ',WithDecryption: true }; --> const singleParam = { Name: '/GitHubAPIKey',WithDecryption: true };

The collection process works and there are numerous entries in the input before this lambda triggers.

Appreciate any trailheads.

TIA.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant