can anybody help me out?

I don't know where this error come from

it seems, but I am not sure of course some problem of versioning

@vinnyataide I would delete your .boot folder (`C:\Users\Vinicius\.boot`) and try the command again. That should clear out any “bad” version of Boot and download the latest stable version again.

@vinnyataide You probably also want to run boot -V (or boot —version) to see what version of Clojure and what version of Boot your system thinks it has installed.

thanks guys. I think this problem is resolved but another error has appeared

I think this is related to dependency conflict?

@vinnyataide Hmm, that's normally just a warning in my experience... You can set the version of Clojure that Boot uses in your .boot/boot.properties file. You don't say what command you used that produced that error, nor what's in your build.boot file.

Working on my PR, https://github.com/boot-clj/boot/pull/549, the question came up where to put the launch-socket-server fn. I initially chose boot.core because that's where launch-nrepl is too. But @martinklepsch mentioned that boot.core may not be ideal as it isn't accessible from code running inside pods. If I had to pick a different namespace, which one should I choose? boot.util? A new one?

@pesterhazy probably a new task with new package (by the way I can add you to powerlaces if you like)

@richiardiandrea sorry didn't catch the context

@richiardiandrea the random assets was mostly a comparison to boot reload which has a case for reload, which I think would be well replaced by a multi method or something

oh ok, I think figwheel has some custom event handler hook in the client. not sure though. The nice thing is that the client is imported "as is"

@richiardiandrea ah, so it's just what Figwheel supports already?

I think I have seen something, I don't know if it is exactly what you are asking though

also, now we can add features to figwheel

and have it in both 😉

@geoffs Now that you are the reigning master of notifications, can I ask you a question? 😄

😂 sure!

when you run a test and it is failing with notify -a, do you hear a sound?

Mmm, last time I checked it was still working...

You mean running tests with like 'watch notify -a test' right?

I am using boot-alt-test this time, which one did you check against?

yeah

Oh, I haven't tried with alt test

the success is playing right

the failure does not

Does it throw an exception on failure?

That's what notify looks for

nope

I think that might be the problem

Probably

ok thanks just wanted to double check again the I have this problem and you don't 🙂

@geoffs is there a way to indicate failure other than throwing? I see why you would no want to throw and it might be good to another way to indicate failure

hmmm, you could have it set a warning. But that gets a different noise than the failure noise. At least it would be different than the success noise though

uhm yeah this can be a good solution

I guess there could also be a failures var with an atom similar to warnings. I think the exception makes sense to me as the general "signal" a build failure mechanism...

also @richiardiandrea I think there is an option in boot-alt-test to throw an exception on failure

yep I saw that, can be a workaround