Skip to content

hey team, comment trigger was sending invalid json for the zondax /bot dispatch#365

Open
mooncitydev wants to merge 1 commit intopaseo-network:mainfrom
mooncitydev:fix-workflow-dispatch-payload
Open

hey team, comment trigger was sending invalid json for the zondax /bot dispatch#365
mooncitydev wants to merge 1 commit intopaseo-network:mainfrom
mooncitydev:fix-workflow-dispatch-payload

Conversation

@mooncitydev
Copy link
Copy Markdown

hey paseo team, checked the comment trigger workflow and found the github workflow_dispatches request body was not valid json: there was a single } at the end so the outer object from the opening { on the -d line was never closed. the repositories dispatch api typically answers with 400 for that, so the zondax remote test job likely never started from /bot... comments.

fix: build the body with jq so the shape is always valid, and pass the pr comment with --arg plus env vars so shell quoting and double quotes in the text do not corrupt the request.

while here removed the echo that referenced a never-set command var (it was not the output name, so the line was a no-op for debugging).

cheers

… dispatch payload was invalid json (only one closing brace so the root object was never finished). the api would have returned 400, so the zondax remote test probably never got triggered from /bot comments.

rebuilt the body with jq so the structure is always valid and the comment text is passed through --arg and env, so a /bot line with double quotes in it does not blow up the shell line anymore.

also removed the old debug echo that used a variable that was never set in that step so it never printed anything useful.

cheers

Made-with: Cursor
@mooncitydev mooncitydev changed the title fix: invalid json in comment trigger dispatch (zondax remote test) hey team, comment trigger was sending invalid json for the zondax /bot dispatch Apr 26, 2026
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

Successfully merging this pull request may close these issues.

1 participant