This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-10-16
Channels
- # aws-lambda (10)
- # beginners (52)
- # boot (42)
- # cider (2)
- # cljs-dev (8)
- # cljsjs (4)
- # cljsrn (10)
- # clojars (3)
- # clojure (48)
- # clojure-conj (4)
- # clojure-dev (19)
- # clojure-italy (7)
- # clojure-norway (4)
- # clojure-russia (44)
- # clojure-spec (70)
- # clojure-uk (34)
- # clojurescript (39)
- # cursive (35)
- # data-science (11)
- # datomic (7)
- # emacs (6)
- # fulcro (2)
- # hoplon (12)
- # jobs (1)
- # juxt (18)
- # lein-figwheel (2)
- # leiningen (4)
- # luminus (9)
- # off-topic (29)
- # om (46)
- # onyx (131)
- # other-languages (24)
- # parinfer (84)
- # pedestal (10)
- # portkey (45)
- # protorepl (1)
- # re-frame (15)
- # reagent (43)
- # ring-swagger (41)
- # schema (6)
- # shadow-cljs (293)
- # slack-help (2)
- # specter (42)
When I call boot repl I get this warning: [WARNING] No nREPL middleware descriptor in metadata of boot.repl$disable_exception_colors@1fc152d, see clojure.tools.middleware/set-descriptor!
I am having a problem with boot. I made a short video of it here: https://www.youtube.com/watch?v=TQsqkzzR-8g&feature=youtu.be&hd=1
You can't use repl
together with watch
You can start repl server, but not repl client together with watch
boot repl -s watch ...
should work (server)
and then you can run boot repl -c
(client) on another terminal
Hm, I see you already tried this
https://github.com/danielsz/system/blob/master/src/system/boot.clj#L54 you probably also need to add auto
option to system
@nick319 I have never seen that, but it looks like there are many things that can go wrong in there. First of all the nRepl WARNING you see is weird. Then system, then eventually boot. I would try to isolate the piece that brakes first. Start maybe loading the project in a plain boot repl. Sorry, I know not that helpful after all
I have just seen the video as well. If you are using watch system
I don't think you will see the REPL in the console (but I have never used system)
@richiardiandrea yes, I think you are right that I won't see the REPL in the console. So I created a client REPL to the server REPL but the client REPL does not see any of the code reloading. I made a video of that as well: https://www.youtube.com/watch?v=AHUOaQWr5ZA
I have a composite task, (deftask ct [] (comp (at) (bt) (target))
. I would like to have the repl running with the environment [i.e. filesets] as it exists between at
and bt
recognizing that there are two states 'pre' or 'post'. It seems like (deftask ct [] (comp (at) (repl) (bt) (target))
might give me part of what I want, but how would I know?
I get the following error when I run boot repl on Windows 10 command line: [WARNING] No nREPL middleware descriptor in metadata of boot.repl$disable_exception_colors@4c415a68, see clojure.tools.middleware/set-descriptor!
That warning appears for Boot REPL on all platforms I believe wherever colorization is disabled. The solution would be for boot.repl/disable-exception-colors
to have metadata of ^{:clojure.tools.middleware/descriptor {}}
I think. @micha @alandipert Does that sound right to you? Is there already a GitHub issue for this?
seancorfield not that i'm aware of, if you feel moved to file one, please do
@nick319 created the issue (thank you!) and I added a comment with my idea for a solution.
@micah @alandipert Any idea how I can handle this issue described here: https://github.com/samestep/boot-refresh/issues/5
@nick319 created the issue (thank you!) and I added a comment with my idea for a solution.
@seancorfield do you know how to enable colorization?
I'd have to go read the Boot docs to answer that...
... https://github.com/boot-clj/boot/blob/ac835cea8c18e926bb843e01579b86e3f30458d2/doc/boot.util.md#colorize-system-default : environment variable BOOT_COLOR
(set to 1
or yes
) -- but bear in mind the standard Windows command window does not support colorization!
@seancorfield cool, thank you
@seancorfield how do I set the BOOT_COLOR env variable in build.boot when there is no key for that variable?
It's an environment variable -- you set it in your environment, outside Boot.
@nick319 I think I am working on a similar issue to #k. Doesn't this require the reloading of class files? The issue is that a new class-loader is required so as to allow the old classes to be discarded. I am writing a dynamic import and documenting it here. https://clojuredocs.org/clojure.core/import It is not quite right but it is getting close. [I actually had a working version but broke it.]
@nick319 The remaining issue is the best way to get the class names. Is it best to use the boot fileset and collect all the class files? or use the ClassReader?
The author of boot-refresh is aware of the problem but says he doesn't know why this problem is happening despite spending time on it: https://github.com/samestep/boot-refresh/issues/5
The author of boot-refresh is aware of the problem but says he doesn't know why this problem is happening despite spending time on it
@nick319 Based on your description it sounds like the problem is on the client side. Does the client need to be refreshed as well?
boot watch refresh repl -c -p 6000
It's an environment variable -- you set it in your environment, outside Boot.