This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-10-11
Channels
- # announcements (5)
- # babashka (43)
- # beginners (78)
- # calva (1)
- # cider (35)
- # clj-kondo (15)
- # clj-otel (3)
- # cljs-dev (2)
- # clojure (24)
- # clojure-denmark (1)
- # clojure-dev (9)
- # clojure-europe (43)
- # clojure-israel (1)
- # clojure-italy (1)
- # clojure-losangeles (3)
- # clojure-nl (1)
- # clojure-norway (54)
- # clojure-romania (1)
- # clojure-uk (2)
- # clojurescript (1)
- # core-async (25)
- # cursive (7)
- # datascript (6)
- # datomic (7)
- # docker (2)
- # emacs (2)
- # events (8)
- # exercism (2)
- # fulcro (2)
- # hyperfiddle (16)
- # lsp (46)
- # malli (10)
- # membrane (2)
- # music (6)
- # nbb (30)
- # off-topic (49)
- # polylith (4)
- # reagent (3)
- # releases (4)
- # shadow-cljs (5)
- # slack-help (1)
- # sql (2)
- # testing (2)
- # timbre (6)
- # tools-deps (29)
- # xtdb (36)
Hello, what is happening here?
Warnings in Library Code:
taoensso.encore/compile-ns-filter is deprecated
taoensso.encore/rate-limiter* is deprecated
taoensso.encore/rate-limiter* is deprecated
taoensso.encore/rate-limiter* is deprecated
taoensso.encore/distinctv is deprecated
taoensso.encore/-swap-val! is deprecated
taoensso.encore/sub-indexes is deprecated
taoensso.encore/sub-indexes is deprecated
taoensso.encore/sentinel? is deprecated
taoensso.encore/singleton? is deprecated
Hi there, this just means you’re likely running an outdated version of Timbre. There’s no danger (these are just warnings about some deprecated code being used), but you might want to update to remove the warnings.
@U03K8V573EC Can you please share more details re: your tooling and what specifically you’re doing that triggers the warning? Someone else recently reported https://github.com/taoensso/timbre/issues/379 warnings coming from Shadow-CLJS. My initial impression is that it seems like a tooling bug if warnings are being triggered for deprecated vars using deprecated vars - but it’d be helpful to better understand the context.
Yes it’s the same issue, also using shadow here
Thanks for the update, and for creating the upstream issue 👍