Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

file paths with whitespace cause rev parsing to fail with hg #52

Closed
joshuamiller01 opened this issue Sep 2, 2016 · 9 comments
Closed
Labels

Comments

@joshuamiller01
Copy link
Contributor

When parsing a hg revision to extract the changes, parse_status(changes) will try to regex the hg log output with something like 'when /^A (\S+)$/' , but if the path has whitespace in it, it will fail to match the regex and fail the call. This might be a problem with the other repo types (git, svn) as well.

Sample:
A ../../some/path/to/a/file/abcd stuffafteraspace

Maybe it's safe to assume chef repo contents won't have spaces in them, but the repo in play could have all kinds of other crap; maybe it should filter out said crap prior to mapping?

@jaymzh
Copy link
Collaborator

jaymzh commented Sep 2, 2016

This is a dupe of facebook/grocery-delivery#22

Which... ya know people should not do that, which is why we marked it wishlist. Bad engineers, bad.

@jaymzh jaymzh added the wishlist label Sep 2, 2016
@joshuamiller01
Copy link
Contributor Author

@jaymzh is GD handling this more gracefully somehow? for me taste-tester is completely stuck until you dump everything and re upload on a revision that's ahead of the "bad entry"

@jaymzh
Copy link
Collaborator

jaymzh commented Sep 2, 2016

No, gd will get fucked to, we're just smart enough to not put spaces in filenames, cause that's insane.

On September 2, 2016 2:10:09 PM PDT, Joshua Miller notifications@github.com wrote:

@jaymzh is GD handling this more gracefully somehow? for me
taste-tester is completely stuck until you dump everything and re
upload on a revision that's ahead of the "bad entry"

You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
#52 (comment)

Sent from my Android device with K-9 Mail. Please excuse my brevity.

@joshuamiller01
Copy link
Contributor Author

"we" is a pretty strong word.

@jaymzh
Copy link
Collaborator

jaymzh commented Sep 3, 2016

I give you permission to verbally smack down people putting spaces in filenames in our chef repo ;)

@odcinek
Copy link
Contributor

odcinek commented Sep 6, 2016

@jaymzh how lenient are chef-zero and chef-server about what one can put in the path? tt/gd should match exactly that, and leave in user's discretion to narrow it down.

I like my ☃

@jaymzh
Copy link
Collaborator

jaymzh commented Sep 6, 2016

@odcinek they allow it primarily because they work on windows. WHich is why I didn't close this as wontfix it's a valid feature request. However it's wishlist for all the reasons stated.

@joshuamiller01
Copy link
Contributor Author

Got bit for this again today. Turns out "we" aren't smart.

@joshuamiller01
Copy link
Contributor Author

Fixed with #111

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants