FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

Longpath filter bug by lrm29 · Pull Request #6055 · libgit2/libgit2 · GitHub

Longpath filter bug - #6055

Merged
ethomson merged 3 commits into
libgit2:mainfrom
mathworks:longpath_filter_bug
Sep 20, 2021
Merged

ethomson merged 3 commits into
libgit2:mainfrom
mathworks:longpath_filter_bug

Conversation

lrm29 commented Sep 14, 2021

Copy link
Copy Markdown
Contributor

Fixes #6054.

An alternative might be to handle the null git_repository case in the longpath check ((bool) should_validate_longpaths(git_repository *repo)). Could also put an assert on "repo" argument in should_validate_longpaths.

Comment thread tests/win32/longpath.c
Comment thread tests/win32/longpath.c

Copy link
Copy Markdown
Member

Looks good to me - we'll need to ifdef around that new function to prevent unused warnings, but otherwise 👍

Co-authored-by: Edward Thomson <ethomson@github.com>
lrm29 requested a review from ethomson September 15, 2021 20:41
ethomson merged commit 482e385 into libgit2:main Sep 20, 2021

Copy link
Copy Markdown
Member

Thanks for the fix. I changed the unit test a bit in 005c740 to check the contents in the repo to ensure that filtering was applied.

lrm29 deleted the longpath_filter_bug branch September 28, 2021 19:09
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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

git_index_add_bypath fails with "path too long" when longpaths is true and filters are set

2 participants


Back | FazBrowse Home | New Git URL