Failing to checkout out a revision with an unknown base
Open
Nobody has claimed this yet.
hackbot
- Dominant language
- Python
- Stars
- 570
- Forks
- 351
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 65
Description
Example: https://hackbot.moz.tools/runs/16d4c648-693f-4073-be6f-c5ce5aa42b25
In this case it is a stack where the first revision in the stack is based on a commit that seem to not be in the repo.
UnresolvedCommitError: Cannot expand 0a336b1a481b to a full commit hash: Diffusion does not know one; the commit may not be imported, e.g. an unlanded parent of a stacked patch.
Related: https://bugzilla.mozilla.org/show_bug.cgi?id=2068637
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked Hackbot run and its UnresolvedCommitError, then trace the checkout path that resolves the base revision. Read the related Bugzilla issue 2068637 for the expected behavior when a stack begins from an unknown or unimported commit; done means this case is handled consistently rather than failing unexpectedly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100