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

Invalid cider-repl-history file prevents cider-jack-in from working #2436

Closed
TimoFreiberg opened this issue Sep 5, 2018 · 5 comments · Fixed by #3429
Closed

Invalid cider-repl-history file prevents cider-jack-in from working #2436

TimoFreiberg opened this issue Sep 5, 2018 · 5 comments · Fixed by #3429
Labels
bug good first issue A simple tasks suitable for first-time contributors

Comments

@TimoFreiberg
Copy link

Expected behavior

If the cider-repl-history file is invalid, CIDER should still work.
If CIDER could clean up invalid parts automatically, I would prefer that, but if that's impossible (or too hard), I would be fine with getting a prompt to clean it up manually.

Actual behavior

If the cider-repl-history file is invalid, CIDER doesn't start with the relatively cryptic error message error in process filter: cider-repl--history-read: End of file during parsing (although Bozhidar recognized the error immediately 😄 )
To get it working again, you have to clean up/delete the file manually.

Steps to reproduce the problem

Use broken-cider-repl-history.txt as your cider-repl-history-file, which has a malformed expression at the end:

(:require [clojure.java.io :as io]
          [datascript.core :as d]
          [mdm-utils
            [service :

Run cider-jack-in-clj

Environment & Version information

CIDER version information

CIDER 0.18.1snapshot (package: 20180903.2111)

Emacs version

GNU Emacs 26.1

Operating system

Arch Linux

@bbatsov bbatsov added the bug label Sep 5, 2018
@vspinu
Copy link
Contributor

vspinu commented Sep 6, 2018

Should be easy to fix, but how the broken entries get into the history in the first place?

@TimoFreiberg
Copy link
Author

Unfortunately I have no idea how it happened.

@stale
Copy link

stale bot commented May 8, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contribution and understanding!

@stale stale bot added the stale label May 8, 2019
@bbatsov bbatsov added the good first issue A simple tasks suitable for first-time contributors label May 12, 2019
@stale stale bot removed the stale label May 12, 2019
@bbatsov
Copy link
Member

bbatsov commented May 12, 2019

I'll add here what's needed to be done - we just need to catch that error and display some message prompting the user to reset their history file.

@sovelten
Copy link

sovelten commented Jun 1, 2021

I was having this problem and solved it by removing the nrepl-history file inside .local/cache

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug good first issue A simple tasks suitable for first-time contributors
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants