This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-03-31
Channels
- # admin-announcements (1)
- # beginners (16)
- # boot (25)
- # braid-chat (7)
- # cider (4)
- # cljsfiddle (6)
- # cljsrn (1)
- # clojure (256)
- # clojure-austin (4)
- # clojure-ireland (1)
- # clojure-poland (15)
- # clojure-russia (80)
- # clojure-uk (2)
- # clojurescript (30)
- # core-async (14)
- # core-typed (3)
- # cursive (35)
- # datomic (1)
- # editors (28)
- # hoplon (32)
- # immutant (1)
- # jobs (8)
- # jobs-discuss (1)
- # juxt (6)
- # leiningen (8)
- # liberator (7)
- # off-topic (16)
- # om (69)
- # onyx (38)
- # re-frame (10)
- # spacemacs (1)
- # untangled (117)
What's the recommended way for a leiningen plugin that uses eval-in-project
to print?
Currently I call leiningen.core.main/info
which works fine.... however this means that I need to inject a dependency on [leiningen "2.6.1"]
into the project vm... I've just had a problem because of a transitive dependency conflict on httpclient (included through aether)...
Is there a better way? I was thinking either:
- A future leiningen version could put the code to print in another artifact that has no external dependencies... that way I could only include what I need.
- The leiningen process could return a sequence of strings - which I print from lein vm
Hi Guys any idea about "REPL server launch timed out.” ?
or how to debug it to find the reason (my bet its netowkring problem)
@andrzejsliwa: firstly you can extend the timeout....
There are usually two places it can happen....
1) At initialisation... i.e. loading clj files... You can debug this by adding :verbose
to your top level ns definition and watching where the printlns as namespaces load slow down.
2) It's because of a function you're calling at initialisation.... e.g. :repl-init
- stop doing it at repl-init... fire up a repl, then performance test through normal methods.
but yeah its probably a networking problem