Skip to content
This repository has been archived by the owner on Jul 2, 2022. It is now read-only.

Repl never prompts #247

Open
1 task done
dchacke opened this issue May 5, 2019 · 11 comments
Open
1 task done

Repl never prompts #247

dchacke opened this issue May 5, 2019 · 11 comments

Comments

@dchacke
Copy link

dchacke commented May 5, 2019

  • I am reporting a bug or problem in Chestnut

I create a new project and then try to launch the repl:

➜ lein new chestnut frontend-two --snapshot +reagent
Generating fresh Chestnut project.
README.md contains instructions to get you started.
➜ cd frontend-two 
➜ lein repl
2019-05-05 01:11:36.976:INFO::main: Logging initialized @2180ms to org.eclipse.jetty.util.log.StdErrLog
[WARNING] No nREPL middleware descriptor in metadata of #'cider.piggieback/wrap-cljs-repl, see clojure.tools.middleware/set-descriptor!
nREPL server started on port 60606 on host 127.0.0.1 - nrepl://127.0.0.1:60606

It says that the repl server has started, but I never actually get a prompt. My terminal just keeps waiting (I gave up after a few minutes).

@featheredtoast
Copy link
Collaborator

Trying to reproduce this - What version(s) of clojure+java is this on?

@dchacke
Copy link
Author

dchacke commented May 5, 2019

Java version 1.8.0_111, Clojure version 1.8.0.

@plexus
Copy link
Owner

plexus commented May 6, 2019

@weltschmerz1 some things to check:

  • is your leiningen the latest version (lein upgrade)?
  • do you have anything in ~/.lein/profiles.clj that could be interfering? (mv ~/.lein/profiles.clj ~/lein/profiles.clj.backup)

@plexus
Copy link
Owner

plexus commented May 6, 2019

Duplicate of #243.

@weltschmerz1 could you also check your current version of leiningen before upgrading (lein version), and tell us your operating system?

@dchacke
Copy link
Author

dchacke commented May 6, 2019

Upgrading from Leiningen 2.7.1 to 2.9.1 fixed it.

@dchacke dchacke closed this as completed May 6, 2019
@dchacke
Copy link
Author

dchacke commented Jun 28, 2019

I'm afraid I can now reproduce this again. Leiningen 2.9.1, Java 1.8.0_111, Clojure 1.10.0.

@dchacke dchacke reopened this Jun 28, 2019
@dchacke
Copy link
Author

dchacke commented Jul 3, 2019

Has anybody had a chance to look into this?

@featheredtoast
Copy link
Collaborator

featheredtoast commented Jul 4, 2019

Not yet - will look into it soon. Was it the new Clojure version that triggered it this time?

@dchacke
Copy link
Author

dchacke commented Jul 4, 2019

I'm trying it out - I changed the Clojure version in project.clj to 1.8.0 to see if that fixes it, but it doesn't. But that could be because I don't know how to properly downgrade.

Does the project need to be created using Clojure 1.8.0? Or should changing it in project.clj after creation do the trick?

@featheredtoast
Copy link
Collaborator

I don't believe either makes a difference - Clojure version change might be a red herring, but I'll see if I can reproduce it under the same environment.

@whenmoon
Copy link

whenmoon commented Sep 4, 2019

Was there ever a fix for this?

# for free to subscribe to this conversation on GitHub. Already have an account? #.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants