This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-01-19
Channels
- # adventofcode (7)
- # aws (6)
- # babashka (7)
- # beginners (200)
- # calva (49)
- # chlorine-clover (3)
- # cider (24)
- # clj-kondo (115)
- # cljs-dev (5)
- # cljsrn (16)
- # clojure (44)
- # clojure-australia (9)
- # clojure-czech (1)
- # clojure-dev (1)
- # clojure-europe (63)
- # clojure-france (6)
- # clojure-losangeles (1)
- # clojure-nl (2)
- # clojure-spec (27)
- # clojure-uk (77)
- # clojurescript (45)
- # clojurewerkz (3)
- # conjure (5)
- # cryogen (1)
- # cursive (2)
- # datahike (6)
- # datascript (3)
- # datomic (18)
- # fulcro (5)
- # graalvm (55)
- # jobs (3)
- # luminus (4)
- # malli (1)
- # pathom (1)
- # reagent (16)
- # shadow-cljs (67)
- # spacemacs (18)
- # sql (57)
- # testing (6)
- # tools-deps (9)
I'm trying to use luminus for the first time. Most things seem to be working fairly well, apart from one major annoyance. I get this logging output in my REPL once per second:
2021-01-19 11:59:39,252 [XNIO-1 I/O-12] DEBUG io.undertow.websockets.core.request - UT025003: Decoding WebSocket Frame with opCode 1
Is there an easy way to get rid of this?
https://luminusweb.com/docs/logging.html AIUI you can either raise the root log level (past DEBUG) or you can set the logging level of undertow
<logger name="io.undertow.websockets" level="warn" />
Appears to silence that message for me.Thank you! I ended up doing that, too, but I wish I could do something less brutal than silencing all debug level log entries.
Looks like luminus uses timbre as a wrapper as well, and timbre mentions more specific filters, ie by namespace and log level. http://ptaoussanis.github.io/timbre/taoensso.timbre.html#var-default-config or https://github.com/ptaoussanis/timbre#log-levels-and-ns-filters-basics Might have a solution for you, and probably nicer than XML configs