-
-
Notifications
You must be signed in to change notification settings - Fork 25
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
Failed run ci in action github #116
Comments
it's seems related to this RDJSON implementation #111 |
@brunoalvesdasilva #118 might help you diagnose this |
@davidcornu Of course, I'll try to update, the only problem is that a package indicated by stylelint is deprecated to work with jsx, we're still working on that. I'll add the pull request code and let you know if everything went well |
Can someone look at it? this action is still completely broken in CI.... |
With the latest release that contains @davidcornu's changes, you should be able to see any errors that Stylelint runs into. @taltcher, on v1.22.1, are you getting an error from Stylelint printed out? Or are you still receiving the "failed to unmarshal rdjson" error? |
@bert-mccutchen - I'm getting:
|
@bert-mccutchen - is there any additional information I can provide? |
@taltcher which version of |
@davidcornu latest one |
@taltcher hmm ok that would suggest you're hitting a case my PR didn't handle. The way I debugged this was to fork the repo, add a bunch of extra logging, and update the gh actions step to use the fork. This helped me realize there was a stylelint error being passed to reviewdog. You might have success doing something similar. |
@davidcornu you want me to try and run the forked branch as well? which branch is it? |
Hi @davidcornu - I have validated again that I'm on the latest version of |
@taltcher gonna mark this one as closed. Feel free to reopen. |
Hello everyone, I have a question.
We are receiving this error in our company's action, and apparently we have not made any changes.
Is there anything we can do to solve it? We temporarily fixed the version at 1.18.1 and it is correct, but in the last version it does not work, always generating this error.
in action code:
The text was updated successfully, but these errors were encountered: