-
-
Notifications
You must be signed in to change notification settings - Fork 217
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
Babashka Jack-In REPL doesn't show eval errors #1413
Comments
I got the same problem. VSCode1.62.3 + Calva 2.0.228 + nrepl 0.6. When use I suspect it is about the VSCode version, because my last VSCode version is fine, after the auto update of that, the problem came out. |
looks I got fixed... I just downgrade the calva to 2.0.225.. So it maybe a new version bug |
Thanks for investigating it some more, @Hzqi ! I did think it was strange I haven't noticed this before... Does this extra info ring any bells for you, @bpringe, @marcomorain ? |
This is caused by the error handling code that I added. I can reproduce and I'm debugging now. |
When the user is using a NREPL connection that doesn't have the cider-nrepl middleware loaded, we cannot reply on the `stacktrace` middleware being present. Handle the missing middleware gracefully. Fixes: BetterThanTomorrow#1413
When the user is using a NREPL connection that doesn't have the cider-nrepl middleware loaded, we cannot reply on the `stacktrace` middleware being present. Handle the missing middleware gracefully. Fixes: BetterThanTomorrow#1413
When the user is using a NREPL connection that doesn't have the cider-nrepl middleware loaded, we cannot reply on the `stacktrace` middleware being present. Handle the missing middleware gracefully. Fixes: BetterThanTomorrow#1413
With VSCode + Calva 2.0.227 + Babashka 0.6.7, the Jack-In REPL won't show errors (or do anything else visible) while evaluating forms with problems. Well-written forms evaluate normally.
Here's the output with nREPL logging enabled where I evaluated two forms
(+ 1 1)
and(nosuchsymbol)
(I've left out some repetitive content, but I also noticed there were duplicate autocomplete messages):The text was updated successfully, but these errors were encountered: