Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Log a warning when git's version can't be parsed

See original GitHub issue

Would it make sense to have a logger.debug (or logger.info/warning) call here mentioning that the version couldn’t be parsed ?

_Originally posted by @xavfernandez in https://github.com/pypa/pip/pull/10117#discussion_r688786750_

Yes, let’s do a warning. 😃

Issue Analytics

State:
Created 2 years ago
Comments:13 (8 by maintainers)

Top GitHub Comments

2reactions

uranusjrcommented, Aug 27, 2021

@aniketh-varma Feel free! You’d want to follow instructions to set up a development environment, change the code in git.py, and add a test for the error message.

1reaction

DiddiLeijacommented, Jan 21, 2022

Hey @Hermit97, thanks for offering. There is already a PR to close this at #10801.

Top Results From Across the Web

Could not parse git.exe version number - Stack Overflow

I have setup git 1.8 and linked it (through settings) into TortoiseGit but it's being painful....

git-rev-parse Documentation - Git

Use git rev-parse in option parsing mode (see PARSEOPT section below). ... A revision parameter <rev> typically, but not necessarily, names a commit...

Git Hooks | Atlassian Git Tutorial

Git Hooks are scripts that run automatically every time a particular event ... git rev-parse HEAD to get the new commit's SHA1 hash,...

Troubleshooting CI/CD - GitLab Docs

This occurs because the previous pipeline cannot find a checkout-SHA ... Pipeline configuration warnings are shown when you: ... Job log slow to...

simple-git - npm

The properties of git log are fetched using the --pretty=format argument which supports different tokens depending on the version of git - for ......