-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
magit-status
fails, initially with error regarding transient-switch-frame
, then subsequently with cl-no-applicable-method
regarding forge-get-repository, :known?
#16647
Comments
Limiting the git layer to the following packages allows magit to function as expected. (git :packages magit magit-section evil-collection evil-surround git-timemachine transient) ;; provides magit |
Same issue, can confirm |
Performing a package rollback & updating again seems to fix it somehow |
That's interesting. A rollback did not work for me, regardless of how far back I went. |
Have you tried re-applying the updates after rolling back? IIRC rollbacks alone didn't fix it for me. |
@sunlin7 This might also be related to load-hints. I can reproduce the error, but setting |
I'm going to reproduce the issue, give me some time, will update later. thanks
|
I tried reproduce this issue but it dose not happened on my local environment (Emacs-29.4, Ubuntu 20.04). |
@bryce-carson Dose the #16654 works for you? Thanks |
I'll try that today. |
Quick fix: add add forge to dotspacemacs-excluded-packages |
I apologize, I still have not tried #16654 to test if it resolves the issue. When I will try it I cannot say, nor would it be a perfect test of if the merged PR resolves this issue: I upgraded my Fedora installation and I have a newer Emacs now than I did then, and I don't have notes on what exact installation I had. For situations like these I almost wish I used GUIX to manage my software rather than DNF, so I could install a different set of software and replicate the old environment without issue. |
I think such errors usually come from incorrect byte compilation, for example when an outdated version of a dependency was loaded before compiling another package depending on the updated dependency. We should investigate whether we can do something about this in Spacemacs, or if this needs to be fixed upstream in package.el. In this specific case, M-x package-delete magit, forge (and perhaps magit-section for good measure), and reinstalling them by restarting should resolve the errors. |
Confirmed in my setup. Deleting and reinstalling magit-* and forge fixes this issue. |
Description
After updating Spacemacs and my packages November 7th 2024, I haven't been able to use magit at all.
Reproduction guide 🪲
SPC g s
to runmagit-status
and select the current directory, whichcontains the repository. Observe the first quoted message.
magit-status
again (SPC g s
); observe the second quoted message.Alternatively,
SPC g s
to runmagit-status
and select a directory containing a Gitrepository using the minibuffer. Observe the first quoted message.
magit-status
again (SPC g s
); observe the second quoted message.Observed behaviour: 👀 💔
A differnet message is displayed after the first usage of
magit-status
and subsequent usages.Invalid slot name: "#<transient-prefix transient-prefix-8890634>", :transient-switch-frame
.cl-no-applicable-method: No applicable method: forge-get-repository, :known?
.Expected behaviour: ❤️ 😄
Magit status buffer should open for the selected repository.
System Info 💻
Backtrace 🐾
The text was updated successfully, but these errors were encountered: