Fork me on GitHub
#boot
<
2017-10-16
>
Mudge05:10:15

@dominicm thanks! that did hellp

Mudge06:10: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!

Mudge06:10:47

Anybody know why I get that warning?

Mudge15:10:09

I am having a problem with boot. I made a short video of it here: https://www.youtube.com/watch?v=TQsqkzzR-8g&amp;feature=youtu.be&amp;hd=1

juhoteperi16:10:54

You can't use repl together with watch

juhoteperi16:10:08

You can start repl server, but not repl client together with watch

juhoteperi16:10:33

boot repl -s watch ... should work (server)

juhoteperi16:10:48

and then you can run boot repl -c (client) on another terminal

juhoteperi16:10:50

Hm, I see you already tried this

Mudge15:10:25

Any help in fixing this problem is appreciated.

richiardiandrea16:10:46

@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

richiardiandrea16:10:53

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)

Mudge16:10:58

@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

phreed18:10:09

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?

Mudge19:10:51

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!

Mudge19:10:02

Any idea how to fix it?

seancorfield19:10:23

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?

alandipert20:10:00

seancorfield not that i'm aware of, if you feel moved to file one, please do

seancorfield20:10:06

@nick319 created the issue (thank you!) and I added a comment with my idea for a solution.

Mudge22:10:06

cool, thank you

Mudge20:10:29

I made a github issue about this today

Mudge20:10:05

@micah @alandipert Any idea how I can handle this issue described here: https://github.com/samestep/boot-refresh/issues/5

seancorfield20:10:06

@nick319 created the issue (thank you!) and I added a comment with my idea for a solution.

Mudge20:10:32

@seancorfield do you know how to enable colorization?

seancorfield21:10:43

I'd have to go read the Boot docs to answer that...

seancorfield21:10:14

... 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!

Mudge21:10:37

@seancorfield how do I set the BOOT_COLOR env variable in build.boot when there is no key for that variable?

seancorfield23:10:06

It's an environment variable -- you set it in your environment, outside Boot.

phreed22:10:57

@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.]

phreed22:10:45

@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?

Mudge22:10:11

@phreed that is really exciting! I am eager to try it out when it is ready.

Mudge22:10:00

@phreed I am actually having trouble reloading clojure source files, not java classes

Mudge22:10:30

@phreed you can see the issue here:

phreed22:10:58

@nick319 What does the client connection command look like?

Mudge22:10:54

@phreed It looks like this: boot repl -c -p 6000

Mudge22:10:09

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

Mudge22:10:34

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

phreed22:10:07

@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

Mudge22:10:08

@phreed I tried it. It doesn't work.

seancorfield23:10:06

It's an environment variable -- you set it in your environment, outside Boot.