Here is the relevant content of my pre-receive hook file:
\nfrom git import Repo\n\nrepo = Repo(\"/home/ldt/Projects/dns/dns/.git\")\nprint(repo.git_dir)\nprint(repo.head.abspath)\nprint(repo.head.commit)\nHowever, when I trigger this with a push, this is the result:
\nEnumerating objects: 12, done.\nCounting objects: 100% (12/12), done.\nDelta compression using up to 4 threads\nCompressing objects: 100% (9/9), done.\nWriting objects: 100% (9/9), 876 bytes | 876.00 KiB/s, done.\nTotal 9 (delta 6), reused 0 (delta 0)\nremote: /home/ldt/Projects/dns/dns/.git\nremote: /home/ldt/Projects/dns/dns/.git/HEAD\nremote: Traceback (most recent call last):\nremote: File \"hooks/pre-receive\", line 11, in <module>\nremote: print(repo.head.commit)\nremote: File \"/home/ldt/.virtualenvs/dns-0cwPatsd-py3.8/lib/python3.8/site-packages/git/refs/symbolic.py\", line 197, in _get_commit\nremote: obj = self._get_object()\nremote: File \"/home/ldt/.virtualenvs/dns-0cwPatsd-py3.8/lib/python3.8/site-packages/git/refs/symbolic.py\", line 190, in _get_object\nremote: return Object.new_from_sha(self.repo, hex_to_bin(self.dereference_recursive(self.repo, self.path)))\nremote: File \"/home/ldt/.virtualenvs/dns-0cwPatsd-py3.8/lib/python3.8/site-packages/git/objects/base.py\", line 64, in new_from_sha\nremote: oinfo = repo.odb.info(sha1)\nremote: File \"/home/ldt/.virtualenvs/dns-0cwPatsd-py3.8/lib/python3.8/site-packages/git/db.py\", line 37, in info\nremote: hexsha, typename, size = self._git.get_object_header(bin_to_hex(sha))\nremote: File \"/home/ldt/.virtualenvs/dns-0cwPatsd-py3.8/lib/python3.8/site-packages/git/cmd.py\", line 1074, in get_object_header\nremote: return self.__get_object_header(cmd, ref)\nremote: File \"/home/ldt/.virtualenvs/dns-0cwPatsd-py3.8/lib/python3.8/site-packages/git/cmd.py\", line 1063, in __get_object_header\nremote: return self._parse_object_header(cmd.stdout.readline())\nremote: File \"/home/ldt/.virtualenvs/dns-0cwPatsd-py3.8/lib/python3.8/site-packages/git/cmd.py\", line 1025, in _parse_object_header\nremote: raise ValueError(\"SHA could not be resolved, git returned: %r\" % (header_line.strip()))\nremote: ValueError: SHA could not be resolved, git returned: b''\nI don't get it... How could it work in the REPL but not in code? Could there be some sort of difference in the shell environment that GitPython uses? But if so, what?
","upvoteCount":1,"answerCount":6,"acceptedAnswer":{"@type":"Answer","text":"Thanks for the heads-up. Since it's something with the way GitPython obtains object information, you could try to instantiate the repository with a different object database implementation.
\nThe one implemented in pure python would certainly provide better error messages, maybe it works even.
\nSomething I can imagine to be the reason for this issue in the first place is a different run environment, as the git command is influenced by plenty of environment variables which are set in hooks only.
-
|
I'm trying to write a pre-receive hook. When using the repl, I get the following results: Here is the relevant content of my pre-receive hook file: However, when I trigger this with a push, this is the result: I don't get it... How could it work in the REPL but not in code? Could there be some sort of difference in the shell environment that GitPython uses? But if so, what? |
Beta Was this translation helpful? Give feedback.
Replies: 6 comments
-
|
Further digging has revealed that the problem indeed lies in the fact that, when the hook runs the code, cmd.stdout.readline() just returns a blank... |
Beta Was this translation helpful? Give feedback.
-
|
To me it looks like My expectation would be that the above works though. |
Beta Was this translation helpful? Give feedback.
-
|
OK, so I put the same code into a pre-commit hook and that did not fail. So that makes it pretty obvious to me that it is not the shell environment, but rather the state of the repository during the pre-receive hook that is at fault. I have tried the debugging settings, but unfortunately, it seems this particular command does not get debugged properly: As you can see, some early git commands do get logged but not the one that gives no output... Something else I tried was putting the repo into the pre-receive state by making a pre-receive hook that just looped infintely ( |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the heads-up. Since it's something with the way GitPython obtains object information, you could try to instantiate the repository with a different object database implementation. The one implemented in pure python would certainly provide better error messages, maybe it works even. Something I can imagine to be the reason for this issue in the first place is a different run environment, as the |
Beta Was this translation helpful? Give feedback.
-
|
Well now, using the As for the environment, I did dump |
Beta Was this translation helpful? Give feedback.
-
|
Thanks again! Please allow me nonetheless to close this issue as answered question due to the discovery of a workaround. Hopefully people will be able to find it when encountering similar issues. In order to reopen, there should be script(s) to make this issue reproducible. |
Beta Was this translation helpful? Give feedback.
Thanks for the heads-up. Since it's something with the way GitPython obtains object information, you could try to instantiate the repository with a different object database implementation.
The one implemented in pure python would certainly provide better error messages, maybe it works even.
Something I can imagine to be the reason for this issue in the first place is a different run environment, as the
gitcommand is influenced by plenty of environment variables which are set in hooks only.