I wanted to like this tool, but it seems a bit unpolished still. Apparently it doesn't support 3.6 at all, I just got a backtrace about an extra parameter to some subprocess call. Figuring it was a version issue I switched to 3.8, which got past that, but then when I tried to compare 2 branches that I hadn't checked out locally yet I got a different traceback, ending in:
File "/home/lol/.pyenv/versions/3.8.3/lib/python3.8/site-packages/gomp/gomp.py", line 132, in find_first_common_hash
if source_commit[i][0] == _hash:
IndexError: list index out of range
Then, after checking out those 2 branches, I got the table but the commit msgs were cut off from the front, here's an example:
874464e s bug
There's obviously something before that s.
This isn't a support forum obviously, but just something to be aware of.
I was interested in this because we have the issue of trying to figure out the new commits between releases. We have a branch with cherry-picks per release, and so enumerating new commits between these 2 branches isn't straightforward or even necessarily well defined.
I will look into all of that. One thing I have learned today is that while an internal tool might be extremely battle-tested against a narrow slice of use cases and environments, public scrutiny will uncover numerous issues.
File "/home/lol/.pyenv/versions/3.8.3/lib/python3.8/site-packages/gomp/gomp.py", line 132, in find_first_common_hash if source_commit[i][0] == _hash: IndexError: list index out of range
Then, after checking out those 2 branches, I got the table but the commit msgs were cut off from the front, here's an example:
874464e s bug
There's obviously something before that s.
This isn't a support forum obviously, but just something to be aware of.
I was interested in this because we have the issue of trying to figure out the new commits between releases. We have a branch with cherry-picks per release, and so enumerating new commits between these 2 branches isn't straightforward or even necessarily well defined.