-
Notifications
You must be signed in to change notification settings - Fork 337
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crash after GC in Git #815
Comments
Here's a test script I've used for this (to be run in an empty temporary directory):
|
martinvonz
added a commit
that referenced
this issue
Dec 3, 2022
To prevent git's GC from breaking a repo, we already add a git ref to commits we create in the git backend. However, we don't add refs to commits we import from git. This fixes that. Closes #815.
martinvonz
added a commit
that referenced
this issue
Dec 3, 2022
To prevent git's GC from breaking a repo, we already add a git ref to commits we create in the git backend. However, we don't add refs to commits we import from git. This fixes that. Closes #815.
martinvonz
added a commit
that referenced
this issue
Dec 4, 2022
To prevent git's GC from breaking a repo, we already add a git ref to commits we create in the git backend. However, we don't add refs to commits we import from git. This fixes that. Closes #815.
martinvonz
added a commit
that referenced
this issue
Dec 4, 2022
To prevent git's GC from breaking a repo, we already add a git ref to commits we create in the git backend. However, we don't add refs to commits we import from git. This fixes that. Closes #815.
martinvonz
added a commit
that referenced
this issue
Dec 4, 2022
To prevent git's GC from breaking a repo, we already add a git ref to commits we create in the git backend. However, we don't add refs to commits we import from git. This fixes that. Closes #815.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
After importing a commit from Git, if that commit gets unreferenced and GC'd by Git,
jj
may crash.Reported on Discord by @tp-woven.
Steps to Reproduce the Problem
main
. Check outmain~
.main
branch (git branch -f main
) and force GC (git -c gc.reflogExpire=now gc --prune=now
)jj log
Expected Behavior
jj log
works fine and still sees the old location of themain
branch (since we didn't re-import)Actual Behavior
Crash:
Specifications
The text was updated successfully, but these errors were encountered: