fix(trace): Fixed infinite line-wrapping#529
Draft
lethalbit wants to merge 1 commit intohawkw:mainfrom
Draft
Conversation
There was a fun bug where if the offset in the line-wrapping was ever 0, it would never force a hard-wrap at the limit and also set the line back to itself in the slice. As such it would just hopelessly spin forever trying its best to wrap a line. This bug would also happen if the character that landed *right* on the end of the wrapping boundary was whitespace, causing the offset to be 0.
Owner
|
Thank you for looking at this! We could probably also write some tests for this stuff (running on the development system with |
Author
Collaborator
|
oh! i ended up making a similar change in #551, but:
totally missed that. that bug's still there. |
Author
|
I think I fixed this on my end months ago and just forgor to update this PR, I can do so and update this PR or just drop this one and it can be done elsewhere, i'm good with whatever, just let me know |
This file contains hidden or 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
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.


Within
Writer::write_strthere is a bug in the line wrapping logic, where if theoffsetis ever0, it would never force a hard-wrap and cause the poor line wrapping code to spin forever, hopelessly trying its best, but making no progress.There are 2 cases where
offsetcan be0, the first is when it can't find any whitespace to wrap on, and the second being when the very last character of the wrap boundary was whitespace.This fixes the primary problem by always forcing an ugly hard-wrap at the boundary if
offsetis ever0, and updating theoffsetvalue to be that boundary limit. This then allows the sub-slice of the line to work as expected and not run in circles forever.EDIT: Turns out there are still a few edge cases, i'll keep poking it :v