This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-11-02
Channels
- # announcements (3)
- # aws (8)
- # babashka (87)
- # babashka-sci-dev (3)
- # beginners (34)
- # calva (35)
- # clerk (2)
- # clj-commons (47)
- # cljdoc (10)
- # cljs-dev (21)
- # clojure (19)
- # clojure-android (1)
- # clojure-austin (2)
- # clojure-europe (30)
- # clojure-nl (1)
- # clojure-norway (67)
- # clojure-uk (9)
- # clojuredesign-podcast (7)
- # clojurescript (24)
- # code-reviews (20)
- # cursive (6)
- # datomic (12)
- # emacs (14)
- # events (1)
- # fulcro (7)
- # gratitude (1)
- # hoplon (8)
- # hyperfiddle (23)
- # juxt (22)
- # meander (11)
- # nyc (3)
- # overtone (2)
- # podcasts-discuss (1)
- # reagent (3)
- # releases (1)
- # sci (27)
- # shadow-cljs (73)
- # squint (4)
- # thejaloniki (3)
- # xtdb (7)
running in xtdb 1.24.1 in docker, and jetty doesn’t seem to respect the logback.xml configuration. does anyone know how to get jetty to stop logging debug?
Hey @U0FVDNE9X I've not heard anyone describe this problem before. Do other namespaces respect the logback.xml config okay? are you building the container along the lines of this (+ surrounding example context) https://github.com/xtdb/xtdb/blob/f65c4a398584ec03830509baa2085f3a880a1694/build/docker/Dockerfile#L14
ultimately i realized it wasn’t picking up the logback.xml at all. i was basing my solution off of xtdb/build/deps-standalone-rocksdb.edn and narrowed it down to https://github.com/xtdb/xtdb/blob/f65c4a398584ec03830509baa2085f3a880a1694/build/deps-standalone-rocksdb.edn#L1
it should be paths not path
now that it’s picking up the logback.xml i’m not getting the jetty debug.