ignore spaces in .gitignore files#4386
Conversation
|
Agree that we should ignore trailing spaces, but can you look at the two test failures that this introduces? In particular, we want to make sure that we don't regress on carriage return handling. It's not uncommon to have a carriage return at the end of a filename (Mac OS uses the metadata file |
21c45e2 to
b0b4f80
Compare
|
Ah, the test suite was segfaulting for me before it got to the status tests, so I didn't see those failures. Let's try it this way... |
|
The test suite was segfaulting? :/ hopefully in the |
| } | ||
|
|
||
| match->flags = GIT_ATTR_FNMATCH_ALLOWSPACE | GIT_ATTR_FNMATCH_ALLOWNEG; | ||
| match->flags = GIT_ATTR_FNMATCH_ALLOWNEG | GIT_ATTR_FNMATCH_ALLOWSPACE; |
There was a problem hiding this comment.
Is there a reason these need to change order?
|
The tests from #2688 though they're in status, should be enough to make sure we don't regress the odd macOS naming. |
|
Nope, in refs::iterator. But maybe there's just something funny in my working tree. |
b0b4f80 to
5cb6a2c
Compare
|
There shouldn't be anything so funny that we crash. 😥 Would love any details you can provide. |
|
I only get it when running the whole suite, as far as I can tell. Here's a backtrace: Thread 1 "libgit2_clar" received signal SIGSEGV, Segmentation fault. |
|
The existing plus new tests are passing, so I'm going to merge this. Thanks. The stack trace for your error suggests a double-free, though it's pretty odd since CI isn't having issues. Running the test suite under |
... as git itself does.