-
Notifications
You must be signed in to change notification settings - Fork 139
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
"Validation failed" creating prettier checks #718
Comments
Another check in the same repo (eslint: true) passes successfully, so it's not a permission issue. It's only an issue for prettier: true check
|
How can I get the payload for the HTTP post to debug? |
I managed to extract the payload that was causing the 422 error. The issue is "path" is a required field, but not included. {
"name":"Prettier",
"head_sha":"8926cd754ef3fc50cf4f605b55fa686f4da2630c",
"conclusion":"failure",
"output":{
"title":"1 error",
"summary":"Prettier found 1 error",
"annotations":[
{
"path":"",
"start_line":1,
"end_line":1,
"annotation_level":"failure",
"message":"There are issues with this file's formatting, please run Prettier to fix the errors"
}
]
}
} |
I've tracked the issue to prettier itself; prettier/prettier#13516 I think this module could respond a bit better to prettier erroring. In linters/prettier.js we have this code.
However in this case, output.stdout is blank (hence path being an empty string), with the error being in output.stderr. |
Updating prettier in my project seemed to solve the issue. I'll close this, sorry for the noise! |
I've suggested a minor improvement at #722 to prevent invalid checks being pushed. |
Checking output.stderror this is that value. Should I bother to parse this?
I could regexp the first line and extract path, error, line, character? |
I have this output in my github actions logs
Here is the job for this check
Any idea why we are getting
Validation Failed
on the check creation? It seems to be lint-action is generating a bad api payload, but I'm not sure how to debug this.The text was updated successfully, but these errors were encountered: