Proper truncation #18
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tessereth
force-pushed
the
proper-truncation
branch
3 times, most recently
from
68d3d73
to
7c7885d
Compare
tessereth
force-pushed
the
proper-truncation
branch
from
7c7885d
to
2ad2e4e
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When the markdown body exceeds the 50 kilobyte max size, this truncates the number of failures included for each input. All inputs are truncated to the same length. Uses binary search to find the optimal truncation value. If the binary search optimization fails, there's not a whole lot I can do so I ask the user to report it as a bug.
Also:
bin/run-devto create sample html files using CSS from buildkite for easier developmentCloses #15