-
-
Notifications
You must be signed in to change notification settings - Fork 645
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
(error "Cyclic keymap inheritance")
on cider-test-run-test
#3195
Comments
Same for me (I don't even have to had a failing test beforhand though). Same macOS version but a newer emacs version:
Only other difference is that I use Java 11 instead of 18:
|
That's very strange.. I don't see how there could be any problem with keymap inheritance here and I've been using this commit since 2020 without any issues. |
Just have tried and it fixed the problem for me. P. S: Also I've tried to remove .elc files without reverting commit and it didn't help. |
FWIW: I've installed the update via vanilla |
The only other thing I can think of is some interaction with an external package like evil-collection or Spacemacs' keybinding system I can't reproduce it on my end, either on a bare |
I have the same issue and I do use evil-collection.
Edit: Add Emacs version |
I use vanilla emacs without evil. |
This reverts commit 9cac658. The change resulted in "Cyclic keymap inheritance" errors for some users, see clojure-emacs#3195,
Vanilla Emacs without evil here, too.
@yuhan0 Are you on a version >= 28.1 already? Note that all reported Emacs versions so far are in that range. |
Oh... that could be it
|
I am getting the same issue. I use vanilla emacs and I'm on version 27.2 (Emacs version) |
clojure-emacs/cider#3195 Manually 'revert' commit clojure-emacs/cider@9cac658
@chrishowejones Doesn't removing the byte-compiled code fix the issue? |
@bbatsov: see #3195 (comment), from his input it doesn't look like it's the case |
OK, I guess I'll merge the patch that reverses this. Still, I'm puzzled that it seems the bug affected relatively few people, so there must be something we're missing in our analysis of it. |
@bbatsov sorry it took a while to get back to you Bug but removing the .elc files made no difference to me. So I think your workaround of the patch is probably warranted. When I apply the 'revert' of that commit manually the problem doesn't manifest. Without that patch, I can consistently replicate the issue by getting any test to fail and then fixing it so I too am puzzled as to why it's affecting relatively few. Maybe an interaction with some other mode or submode I have active in my setup? |
Searching for other instances of this error, I came across the following two: millejoh/emacs-ipython-notebook#181 IIUIC in both cases the fix was to prevent redundant activations of the same mode? Maybe you can make more sense from this @bbatsov or @yuhan0? |
Just one more instance of this error here - happens after removing byte code as well. It seems like the key binding is working for a while and then starts throwing the above error. Thanks for reverting the commit. |
Just for the record, this problem affected me as well. |
It affected me as well. |
same problem |
Same :-) |
I commented https://github.com/syl20bnr/spacemacs/blob/c6c17748f649236e5c4afab6a0cabb97f0806bf9/layers/%2Blang/clojure/packages.el#L279 and it starts working |
That was a problem - 3907351 - your revert make it work property. As well fix other issues like jumping to failed test. |
The problematic change has been reverted upstream and soon there will be a 1.4.1 release with a few bugfixes. |
Me too. Vanilla 28.1 |
WFM |
Expected behavior
No emacs errors after running
cider-test-run-test
or any othercider-test-*
funciton.Actual behavior
Steps to reproduce the problem
C-c C-t C-t
orcider-test-run-test
q
Environment & Version information
CIDER version information
Emacs version
GNU Emacs 28.1 (build 2, x86_64-apple-darwin21.4.0, NS appkit-2113.40 Version 12.3.1 (Build 21E258)) of 2022-04-28
Operating system
macOS 12.3.1 (21E258)
The text was updated successfully, but these errors were encountered: