This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-08-10
Channels
- # announcements (9)
- # aws (11)
- # babashka (37)
- # beginners (97)
- # biff (2)
- # calva (73)
- # clj-kondo (17)
- # cljfx (3)
- # clojure (89)
- # clojure-europe (45)
- # clojure-norway (12)
- # clojurescript (17)
- # datahike (8)
- # datomic (13)
- # deps-new (4)
- # figwheel-main (1)
- # graalvm (2)
- # hyperfiddle (8)
- # introduce-yourself (6)
- # leiningen (38)
- # lsp (57)
- # malli (13)
- # nbb (46)
- # off-topic (40)
- # pathom (3)
- # polylith (8)
- # rum (4)
- # shadow-cljs (14)
- # spacemacs (1)
- # sql (11)
- # xtdb (10)
FYI, when switching from 0.2.14-alpha
to 0.2.15-alpha
I encountered an EOF error caused by a clojure file I commented out for .. reasons. I figured out which file was the offending one by redefining the file/read-first-statement
fn to give me some feedback on the misbehaving file:
(let [old-fn file/read-first-statement]
(with-redefs [file/read-first-statement
(fn [path]
(try
(old-fn path)
(catch Exception e
(throw (Exception. (str "failed for path: " path))))))]
(let [input (input/extract-params "")]
(-> input command/execute-command))))
Hi @U052A8RUT. Maybe you can send me the file you have problems with, or link to it?
It's just a regular clojure file but commented out entirely. It's not really a bug in 0.2.15, but this kind of invalid clojure file was tolerated in 0.2.14.
Not a big problem but I wanted to let you guys know, in case anyone else encountered it.
Okay, got it. Thanks!
We also ran into this issue