This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-08-01
Channels
- # announcements (1)
- # beginners (71)
- # calva (12)
- # cider (3)
- # clj-kondo (12)
- # cljsrn (9)
- # clojure (167)
- # clojure-dev (21)
- # clojure-europe (5)
- # clojure-italy (60)
- # clojure-nl (6)
- # clojure-spec (6)
- # clojure-uk (60)
- # clojurescript (86)
- # core-async (25)
- # cursive (21)
- # datascript (9)
- # datomic (4)
- # figwheel (8)
- # fulcro (7)
- # graalvm (4)
- # jackdaw (6)
- # jobs (8)
- # juxt (2)
- # leiningen (1)
- # malli (1)
- # off-topic (20)
- # re-frame (31)
- # reagent (5)
- # remote-jobs (3)
- # shadow-cljs (57)
- # sql (6)
- # vim (9)
@lumpy try clearing the caches in the browse - open the dev tools and look through the settings and purge any cache you find. I used to experience the cache showing incorrect pages or getting stuck showing pages from other projects, even after restarting the browser.
I have cleared all caches I can think of. Hard browser cache reset. I did a lein clean and even deleted my .m2 directory. This is not happening when we build a packaged app so figwheel must be involved. Right now only solution is to duplicate / route to /dev.
seems that this dependency entry was causing the issue, removing this entry fixed the problem, adding it back causes it to come back. No idea how that is happening.
[metasoarous/oz "1.6.0-alpha2" :exclusions [[org.clojars.didiercrunch/clojupyter]]]
If I run pgrep java
after a couple of failed attempts there are a bunch of lingering processes.
On further investigation the REPL seems to work more reliably if I use clj -m figwheel.main
.
Is there a major difference between running clj -m figwheel.main
and lein trampoline -m figwheel.main
?