Fork me on GitHub
#boot
<
2015-09-24
>
alandipert00:09:41

i suppose the answer to coordination is to sanction a place in boot proper

micha02:09:34

you're adding the metadata to the file itself?

micha02:09:59

not like as metadata to the file in the fileset?

martinklepsch08:09:56

@micha: yes I did that. Now that you're asking it's probably not a good idea. If subsequent tasks modify the file the metadata will be gone, right?

martinklepsch08:09:45

@micha: the cljs task did that with the output flag so that's why I just followed that example

martinklepsch09:09:44

Would be cool to add a show —usage task that displays information about the JVM process (mem/cpu usage)

martinklepsch09:09:50

@micha: think I misunderstood your earlier question. I add the metadata to the TmpFile objects (as it’s done by boot.core/add-meta)

juhoteperi10:09:29

@martinklepsch: The ideas is that user doesn't want to see the 200 lines of stacktrace when the only interesting info is that there is error on file x on line y

martinklepsch10:09:05

@juhoteperi: tasks like speak expect an exception to inform users about failed builds

juhoteperi10:09:15

Hmph, perhaps it could throw an new exception only containing the message

benzen12:09:17

Hi I,m looking for a way to exclude a particular namespace/file from cljs compilation any recommendation ?

martinklepsch13:09:31

@benzen: is that namespace/file being required by other files?

benzen13:09:17

like discussed on cljs chan yesterday it's a namespace for my devcards

martinklepsch13:09:10

@benzen: can you explain a bit more? why do you want to exclude it?

benzen13:09:57

What i think is happening, is that even if i doesn't call use this namespace in my dev or prod build, the macro still gets executed

benzen13:09:13

And the devcards card ui get started

martinklepsch13:09:27

@benzen: You could try moving your devcards namespace(s) to another source directory.

benzen13:09:58

I think this will do the trick

martinklepsch13:09:09

i.e. now it’s in src/app/devcards/core.cljs and you move it to cards/app/devcards/core.cljs

martinklepsch13:09:01

Then when you want to include the devcards stuff you just call something like (merge-env! :source-paths [ “cards”])

benzen13:09:02

@bhauman: seems to had another way of achieve this

benzen13:09:06

ahhh didn't know about this merge-env! func

martinklepsch13:09:55

@benzen: you could have also used set-env!. Just pass a function instead of a value: (set-env! :source-paths #(conj % “cards”))

benzen13:09:38

ahhahh much better

benzen13:09:12

this way i could keep it simple for the normal build (meaning dev and prod)

benzen13:09:37

and only update it for the devcards task

martinklepsch15:09:13

(someone just reported one…)

martinklepsch15:09:19

There’s so little code and pod pools should clean up after themselves right?

juhoteperi16:09:41

@martinklepsch: Are you still working on hud changes or are the PRs ready?

martinklepsch16:09:09

@juhoteperi: Not working on them right now but I also don’t quite think they’re ready

martinklepsch16:09:47

@juhoteperi: I’d like to get handle-ex right

martinklepsch16:09:09

Or at least get to a point where more than one exception type will be displayed in the hud

alandipert16:09:18

@martinklepsch: i think you need to destroy the pod when you're done

juhoteperi16:09:34

I think that can be changed later

martinklepsch16:09:55

@alandipert: even when I use a pod pool? They should handle destroy when being called with :refresh no?

martinklepsch16:09:17

@juhoteperi: true. if you merge, please open issues for the outstanding stuff so things don’t get lost

juhoteperi16:09:25

@martinklepsch: Okay, I'll merge, change it so that file info etc. is send to client and release snapshots for testing

martinklepsch16:09:59

@podviaznikov: @juhoteperi do I see that correctly that currently perun metadata keys are filenames instead of their path in the fileset?

juhoteperi16:09:42

martinklepsch: Yeah, that could cause problems

martinklepsch16:09:21

one more yak to shave 😄

juhoteperi16:09:32

Hmh I wonder if even Figwheel has info about warning file name and line number

martinklepsch16:09:45

btw, dnolen said those error-message helpers for warnings (lol) could be moved somewhere public.

juhoteperi16:09:07

But I don't know if we need that

juhoteperi16:09:20

Strange, what is adding that line number to the message

martinklepsch16:09:49

it’s the env thats passed to the handler iirc

juhoteperi16:09:03

error-message is used from cljs.analyzer

juhoteperi16:09:13

I thought I already moved those

martinklepsch16:09:30

Can I pass tmp-file records between pods?

martinklepsch16:09:43

^ apparently it’s not possible

alandipert16:09:45

@martinklepsch: yeah you definitely want to destroy the pod when you're done with it, the pool thing can't know when you're done

alandipert16:09:39

err actually, i'm wrong again

alandipert16:09:45

will let @micha come in and clarify lol

alandipert16:09:06

right. sorry for added confusion

juhoteperi17:09:59

Hah I had to do some magic to be able to construct original file path from file in tmp-dir

juhoteperi17:09:21

There was a problem running open-file command: vim --servername saapas --remote-silent "+call cursor(27,0)" src/cljs/frontend/core.cljs

juhoteperi17:09:27

At least now the command is correct

juhoteperi18:09:40

Aha: (.exec (Runtime/getRuntime)) I forgot to add the commad to exec call

juhoteperi18:09:00

Warnings look quite bit better when the filepaths don't include the tmp-dir path simple_smile

xifi20:09:57

@juhoteperi: your README link to boot is pointing to tailrecursion

xifi20:09:20

boot-reload's README to be a bit more specific

juhoteperi20:09:02

The readme hasn't been updated in a year 😄

juhoteperi21:09:58

How should I pronounce boot-cljs 😄 boot clojurescript or boot c l j s 😄

joelkuiper21:09:46

I do the latter, but not sure what the consensus is 😉

mynomoto23:09:32

Does boot has an equivalent to :java-agents [[co.paralleluniverse/quasar-core "0.7.3"]] on a project.clj?