This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-10-06
Channels
- # aleph (79)
- # bangalore-clj (3)
- # beginners (49)
- # boot (74)
- # cider (10)
- # cljs-dev (21)
- # cljsrn (2)
- # clojure (105)
- # clojure-berlin (1)
- # clojure-brasil (1)
- # clojure-dusseldorf (1)
- # clojure-korea (1)
- # clojure-poland (3)
- # clojure-russia (38)
- # clojure-spec (146)
- # clojure-uk (20)
- # clojurescript (70)
- # cloverage (1)
- # component (1)
- # core-async (23)
- # css (16)
- # cursive (22)
- # datascript (1)
- # datomic (22)
- # defnpodcast (6)
- # emacs (60)
- # events (1)
- # hoplon (94)
- # jobs (1)
- # jobs-rus (13)
- # luminus (11)
- # off-topic (11)
- # om (48)
- # onyx (5)
- # proton (7)
- # re-frame (87)
- # reagent (39)
- # rethinkdb (1)
- # ring-swagger (14)
- # rum (6)
- # specter (14)
- # untangled (105)
- # vim (6)
- # yada (22)
am I doing this the wrong way? i have a task that takes a bunch of css files and converts them to cljs files via a command-line executable via dosh
. in order for the shell executable to work, I have to write the files into the fileset before transforming them. afterwords, I’m only interested in the executable’s output, and don’t want to clutter the target output with all the “intermediary” files.
right now I’m doing a bunch of fs queries by-name/by-path/by-re
to remove all the intermediaries, but is there a better way?
i.e. not add them to the fs output in the first place? or somehow query the fs for “only things I’ve added, minus all these things I dont care about”?
… or on second thought, is this unavoidable? what I’m really doing is adding +output to specific files, and when the target
task runs, it’s just moving those output files into a single main.out
dir.
so the real solution is to either not mark those files as +output, or only do further operations (after boot is finished) on main.out, ignoring everything else
@lwhorton are you saying you have one task that creates intermediate files and then another subsequent task that completes processing them, and then after the second task run you no longer want those intermediate files hanging around in the fileset?
but I believe that I misunderstood the fileset’s purpose more generally - the target task just gathers everything under one roof, but those dirs/files that were created during a task hang around
so if I had a task that created
/build/foo.js
/build/bar.js
/build/baz/a.js
the target task would do something like
/build/main.out/foo.js
/build/main.out/bar.js
/build/main.out/baz/a.js
but the root directory would look like
/build/foo.js
/build/bar.js
/build/baz/a.js
/build/main.out
@lwhorton you are looking for the sift
task
you can use that to filter things from the fileset
(sift :to-asset #{#”usefulbut/doesnotwant.js"})
asset files are not put in output from target dir
Wanted to ask an opinion on how to approach error reporting in prod. The log4j2 appender doesnt pretty print and here we don't want to use hosted log services for now. I really would like to avoid rolling my own appender and clojure.logging
does not help.
I know I am finishing off topic, sorry, but this channel is awesome 😄
I’ve been using unilog
recently
I'll check it out, my problem is that I attach a lot of data to ex-info
but then the resulting email/print is very dense and difficult to read
@richiardiandrea i send logs to stdout which is piped to syslog
What if I log an entire ring request? Are you then able to read it or you employ some parsing afterwards?
I have already some logic for converting ex-info to understandable Clojure objects..for instance to unroll the stacktrace
But log4j does not know about that
And I am afraid I will need some custom stuff ..or just like you log as json
like if something goes wrong i may need to feed it back into some process to fix the glitch
Yes for that i do the same, in what we call "bad-events"
But then we receive an emril, which is ugly :)
Yes, that alert
We have so much stuff in it that they always compare it to some Rails report :)
And I need to find a way to dispel that and make it pretty ah ah
Ruby spoiled the good ol' scroll-in-the-terminal style :)
Thanks Micha for your inputs
if only i could devise a foolproof way to silence logging from dependencies and 3rd party code that i use in my applications
@micha doesn't the standard way of doing it with log4j work for you?
I create a logger with the package and raise the level to error here
And the dep logging is gone
Since I have all the set of bindings that log4j2 provides, everything is caught
Ok never tried that one explicitly but I can try it out...at the moment I mute all the hikari db pool stuff, undertow...things that I don't need
I'll report back
yep sure I have it here
the above is for prod
well, staging
Found a project were i do use aws
i almost figured out how to do it with no deps and no xml, but something is missing somewhere
Lol ahah, there must be a way via code..why ""
to .getLogger
? Probably it is not rpplying the level from the root of the packages hieraschy somehow
yeah i don't fully understand how it is supposed to work, there is dependency injection going on
Yes that's true, i just don't know which logger is taken by using ""
i would take just .getRootLogger
Does anyone know how to adjust the boot-cljs task to make a nodejs entrypoint? I’m trying to follow this: https://github.com/clojure/clojurescript/wiki/Quick-Start#running-clojurescript-on-nodejs
Ah I think i might be getting it