-
Notifications
You must be signed in to change notification settings - Fork 357
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
thread 'main' panicked at 'commit.secure_sig was set', lib/src/git_backend.rs:909:9 #2652
Comments
@necauqua, can you look into that? |
I think you can work around it by downgrading to 0.11.0 or at least something that's more than a week or two old. |
For now I've moved the repo and re-cloned. I'm happy to keep this broken repo around to help debug |
Your repo is not broken, it seems that you have a signed child commit that it tries to automatically rebase. And.. atm rewriting a signed commit causes this assert to go off in main, it's a dumb bug that's fixed in #2634 If we want to fix it separately, we just need to add |
Ah, nice. I have just finished my other obligations at my dayjob so I was just about to review that PR. Since Yuya has already reviewed it (thanks!), I don't expect to find anything major, and we can hopefully land that soon. |
Yep, looks good! Now when I ran
and then a log as expected. Thanks both! |
Description
I'm not quite sure how I've got myself into this situation, but any
jj
command is now throwing:Here is with backtraces:
Steps to Reproduce the Problem
I have no idea! The last thing I did was a
jj git fetch
, after GitHub & Mergify automatically merged some pull requests.Expected Behavior
I can use
jj
🙂Actual Behavior
I can't use
jj
at all 😅Specifications
The text was updated successfully, but these errors were encountered: