-
-
Notifications
You must be signed in to change notification settings - Fork 372
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
runDangerSubprocess implementation is incorrect (?) #603
Comments
That could make sense yeah 👍 |
Closed
I just triggered this when I started adding |
I'm also exhibiting this issue, I think because a lot of errors were emitted so the json got big. |
This should be fixed in the latest builds of Danger JS (it came in with all of the GitHub actions support in #697 ) |
Oh great! -- Upgrading Presently! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I encountered an issue, when danger fails on the
validateResults
function (DangerResults.ts
) although the result is actually correct. It throwsResults passed to Danger JS did not include fails
. The result argument passed here is indeed an empty object, however the result has a correct shape at an earlier point, as it's printed to the console.I noticed this only happens if I include markdown to the result, and only if the markdown is bigger than a certain size. This makes me think the subprocess stream is not correctly read here: https://github.com/danger/danger-js/blob/master/source/commands/utils/runDangerSubprocess.ts#L38
Because this code assumes the data will arrive in a single chunk (L43), and if it's not a json string (L41), it won't process the data ever.
Am I thinking right?
The text was updated successfully, but these errors were encountered: