-
-
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
GitHub Comment Length Limit #919
Comments
I think it should already do that, maybe there's some edge cases where it doesn't? |
Is it possible that github’s limit changed? |
That seems unlikely to me, given how much stuff could break - check the source and your repro, to see if you can think of a way? |
I looked through each of the files under the Github Platform, and I couldn't find any that did truncation? Do you have an idea where the implementation of that truncation might be? I mostly looked here: https://github.com/danger/danger-js/blob/master/source/platforms/github I also searched our code for 65536 and I couldn't find that constant anywhere except as a spurious power-of-two constant in an old Issue (unrelated). |
Looking at this debug log I stuck in, it looks like there were a ton of text in one of my fail messages. (I think it's a lot of snapshot failures) |
Ah, maybe it was in danger ruby we built infra to check the length. Hard to keep on top of all the implementations |
The GitHub Integration just fails with a GitHub Error Response if your Issue Comment gets too long.
It’d be great if we truncated the message, & added a
[truncated]
📝?Thoughts @orta ? I’m happy to implement this if you have advice!
The text was updated successfully, but these errors were encountered: