Skip to content
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

Print stacktrace link in REPL gets duplicated #1542

Closed
jacobemcken opened this issue Feb 19, 2022 · 1 comment · Fixed by #1552
Closed

Print stacktrace link in REPL gets duplicated #1542

jacobemcken opened this issue Feb 19, 2022 · 1 comment · Fixed by #1552
Labels
bug Something isn't working evaluation good first issue Good for newcomers output/repl window

Comments

@jacobemcken
Copy link

jacobemcken commented Feb 19, 2022

How to reproduce:

  1. Create empty Clojure project lein new calvabug
  2. Open VS Code and start REPL: Calva: Start a Project REPL and Connect
  3. Trigger any exception e.g. with (/ 4 0)
  4. Close the REPL buffer by clicking the little x or pressing Ctrl+w
  5. Start REPL again: Calva: Start a Project REPL and Connect
  6. Trigger exception again

Expected behavior:
Show "Print stacktrace" a single time.

What actually happens:
The "Print stacktrace" is shown as many times as the REPL was (re-)started.

multiple print stacktrace

@PEZ PEZ added bug Something isn't working evaluation output/repl window labels Feb 19, 2022
@PEZ
Copy link
Collaborator

PEZ commented Feb 19, 2022

I have been wondering about this. I vaguely remember someone speculating that it was about REPL restarts. Should be easy to fix if this is what it is about.

@PEZ PEZ added the good first issue Good for newcomers label Feb 19, 2022
@PEZ PEZ mentioned this issue Feb 20, 2022
14 tasks
@PEZ PEZ linked a pull request Feb 21, 2022 that will close this issue
14 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working evaluation good first issue Good for newcomers output/repl window
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants