Describe the bug
I'm analyzing the github repo avatarify and the commits containing submodule commits such as this one causes an exception to be raised:
ValueError: SHA b'72a32a67dee3a67dff76f565551907a2fc7e88e6' could not be resolved, git returned: b'72a32a67dee3a67dff76f565551907a2fc7e88e6missing'
The hash in the error being the one of the submodule commit.
To Reproduce
I've noticed this issue on 2 occurrences while working with avatarify:
When I use commits = pydriller.Repository(...).traverse_commits()
and retrieve either of dmm_unit_size/dmm_unit_complexity/dmm_unit_interfacing:
for commit in commit:
dmm_unit_size = commit.dmm_unit_size
dmm_unit_complexity = commit.dmm_unit_complexity
dmm_unit_interfacing = commit.dmm_unit_interfacing
This is straightforward to patch on my side as I can just try-catch these metrics and replacing them by None if it fails on a commit. However the second case would require a change out of my reach.
When I call the constructor of pydriller.metrics.process.code_churn.CodeChurn
Unless I avoid the problematic commits by navigating with CodeChurn's from_commit/to_commit around them, I simply cannot compute the repo's churn
OS Version:
Windows
Describe the bug
I'm analyzing the github repo avatarify and the commits containing submodule commits such as this one causes an exception to be raised:
ValueError: SHA b'72a32a67dee3a67dff76f565551907a2fc7e88e6' could not be resolved, git returned: b'72a32a67dee3a67dff76f565551907a2fc7e88e6missing'The hash in the error being the one of the submodule commit.
To Reproduce
I've noticed this issue on 2 occurrences while working with avatarify:
When I use
commits = pydriller.Repository(...).traverse_commits()and retrieve either of dmm_unit_size/dmm_unit_complexity/dmm_unit_interfacing:
This is straightforward to patch on my side as I can just try-catch these metrics and replacing them by None if it fails on a commit. However the second case would require a change out of my reach.
When I call the constructor of
pydriller.metrics.process.code_churn.CodeChurnUnless I avoid the problematic commits by navigating with CodeChurn's from_commit/to_commit around them, I simply cannot compute the repo's churn
OS Version:
Windows