Format sparse v4 directory attributes safely - #175
Open
OskarEichler wants to merge 1 commit into
Open
Conversation
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
1 participant
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.
Problem: SFTP v4 permits optional file attributes, but directory longname formatting assumed permissions, size, and modification time were always present and raised on sparse responses.
Fix: Render missing permissions as unknown bits, use a size placeholder, and leave the timestamp field blank when absent.
Regression coverage: Adds focused upstream cases for sparse v4 attributes. V4 name tests: 7 runs / 13 assertions. Full suite: 434 runs / 1,197 assertions with only the pre-existing Ruby 4 StartTest positional-hash/keyword expectation failure.