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.

Sign up for GitHub

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

Jump to bottom

where could I find console log? #69

Closed
cyberyoung opened this issue Oct 10, 2017 · 5 comments · Fixed by #92
Closed

where could I find console log? #69

cyberyoung opened this issue Oct 10, 2017 · 5 comments · Fixed by #92

Comments

@cyberyoung
Copy link

cyberyoung commented Oct 10, 2017 •
edited
Loading

I used it on my 2 macs, one is ok, the other cannot work(printing "Starting nREPL..." like, forever).
I ps grep java, and found the java process will disappear after a while, so I want to see what happened, but I cannot find any console output.
Thanks
@avli
Copy link
Owner

avli commented Oct 14, 2017

I'd suggest trying the approach described in the second comment in the issue #53. I will appreciate if you share the results.

@cyberyoung
Copy link
Author

cyberyoung commented Oct 16, 2017 •
edited
Loading

found errors as below:

pasted image at 2017_10_16 02_58 pm

@avli
Copy link
Owner

avli commented Oct 26, 2017

@cyberyoung I've recently come upon very similar error which it seems has something to do with the Leiningen options mismatch with the Java version (see this issue).

What Leiningen and Java versions are you using?

@cyberyoung
Copy link
Author

cyberyoung commented Oct 27, 2017 •
edited
Loading

@avli
lein 2.7.1
java 1.8U151

➜ /Users/liyang/workspace/modata/everest git:(develop) >java -version
java version "1.8.0"
Java(TM) SE Runtime Environment (build 1.8.0-b132)
Java HotSpot(TM) 64-Bit Server VM (build 25.0-b70, mixed mode)```

@cyberyoung
Copy link
Author

ok, I finally fixed it using lein from homebrew.
I just found the only difference between my 2 mac is: one use lein from Homebrew(which is ok wieht clojure extension), and the other use the one download directly from https://raw.githubusercontent.com/technomancy/leiningen/master/bin/lein, the latter one will download jar in .lein/self-install.
Not sure if this info can help you to dig he problem.

marcomorain added a commit to marcomorain/clojureVSCode that referenced this issue Feb 7, 2018
@marcomorain
Add a channel for nREPL output to the Output Window
7d08f8f 
Add a channel to show nREPL output to the user. This channel will be
used for the following:

stdout:

Any stdout messages are sent to the channel.

stderr:

Any stderr messages are sent to the channel, and the channel is brought
to the front to make the user aware.

exit:

If the nREPL closes before be we can load the port, then the exit code
is printed to the nREPL output channel, and the channel is brough to the
front.

Fixes avli#52
Fixed avli#69

Also fixes a bug where the 'Starting nREPL' status message would never
clear if the repl failed to start.
@marcomorain marcomorain mentioned this issue Feb 7, 2018
Merged
marcomorain added a commit to marcomorain/clojureVSCode that referenced this issue Feb 7, 2018
@marcomorain
Add a channel for nREPL output to the Output Window
ffd21a9 
Add a channel to show nREPL output to the user. This channel will be
used for the following:

stdout:

Any stdout messages are sent to the channel.

stderr:

Any stderr messages are sent to the channel, and the channel is brought
to the front to make the user aware.

exit:

If the nREPL closes before be we can load the port, then the exit code
is printed to the nREPL output channel, and the channel is brough to the
front.

Fixes avli#52
Fixes avli#53
Fixed avli#69

Also fixes a bug where the 'Starting nREPL' status message would never
clear if the repl failed to start.
@avli avli closed this as completed in #92 Feb 7, 2018
avli pushed a commit that referenced this issue Feb 7, 2018
@marcomorain @avli
Add a channel for nREPL output to the Output Window (#92)
2791b65 
Add a channel to show nREPL output to the user. This channel will be
used for the following:

stdout:

Any stdout messages are sent to the channel.

stderr:

Any stderr messages are sent to the channel, and the channel is brought
to the front to make the user aware.

exit:

If the nREPL closes before be we can load the port, then the exit code
is printed to the nREPL output channel, and the channel is brough to the
front.

Fixes #52
Fixes #53
Fixed #69

Also fixes a bug where the 'Starting nREPL' status message would never
clear if the repl failed to start.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add a channel for nREPL output to the Output Window marcomorain/clojureVSCode
2 participants
@cyberyoung @avli