Repository navigation
Conversation
mathiasrw
marked this pull request as draft
October 23, 2026 13:05
mathiasrw
marked this pull request as ready for review
October 23, 2026 13:21
mathiasrw
added this pull request to stack #841
October 23, 2026 13:56
mathiasrw
marked this pull request as draft
October 23, 2026 14:14
mathiasrw
marked this pull request as ready for review
October 23, 2026 14:24
mathiasrw
marked this pull request as draft
October 23, 2026 15:20
mathiasrw
marked this pull request as ready for review
October 23, 2026 15:23
mathiasrw
removed this pull request from stack #841
October 23, 2026 15:57
mathiasrw
added this pull request to stack #849
October 23, 2026 16:12
mathiasrw
removed this pull request from stack #849
October 23, 2026 16:12
mathiasrw
added this pull request to stack #850
October 23, 2026 16:17
mathiasrw
removed this pull request from stack #850
October 23, 2026 16:47
mathiasrw
added this pull request to stack #853
October 23, 2026 16:51
mathiasrw
force-pushed
the
fix/818
branch
2 times, most recently
from
October 23, 2026 17:00
2c1e121 to
510e6db
Compare
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.
Closes #818
Stacked on #834.
Change
The last one is a path piped in with
echoand-R, without-T. Before, all three said the same, and the last one showed a blank line.--jsa path that can not be read is now an error once in the run. Before it was once for each file, and instatus.errorsas many times.Tests
test/fix/818.test.jsis new. Two tests of--replacement-filehave the new message.yarn test-cipasses.From the review of 23 October.
After the review of 24 October
nope.txt (ENOENT: no such file or directory), and not only the code.my\dir/nope.txtcan be pasted back. Only a path that starts or ends with a space, or has a control char like the line break fromecho, is shown as JSON, so that char can be seen:"nope.txt\n" (ENOENT: …).After the review of 24 October
Closes #847
(EISDIR: illegal operation on a directory), without, read.\u, like"no\u200bpe.txt": the C1 range, the zero-width chars, the line and paragraph separators and the marks for the direction of text. Before, only ASCII control chars and a space at the start or end were shown, so a zero-width space looked like a normal path.Follow-up
re:re.unclearPathfinds a space at the start or the end and the chars that can not be seen in one test,re.invisibleCharsescapes the ones JSON leaves as they are, andre.fileCallInMessageis the end of the message that is told already.unreadable()is nowpathAndReason(), with a plain if in place of the nested ternary. The output is the same.