This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-09-17
Channels
- # announcements (2)
- # aws (7)
- # beginners (46)
- # cider (15)
- # clj-kondo (24)
- # cljs-dev (3)
- # clojure (46)
- # clojure-dev (34)
- # clojure-europe (7)
- # clojure-italy (7)
- # clojure-nl (10)
- # clojure-norway (15)
- # clojure-spec (5)
- # clojure-uk (42)
- # clojuredesign-podcast (1)
- # clojurescript (79)
- # clr (3)
- # core-async (1)
- # cursive (45)
- # data-science (1)
- # datomic (4)
- # fulcro (17)
- # funcool (14)
- # gorilla (2)
- # graphql (30)
- # jackdaw (5)
- # jobs-discuss (8)
- # joker (4)
- # lein-figwheel (1)
- # off-topic (48)
- # pedestal (26)
- # re-frame (36)
- # reagent (18)
- # reitit (6)
- # remote-jobs (4)
- # shadow-cljs (115)
- # tools-deps (62)
- # vim (12)
Why is my cider suddenly trying to connect to http://clojuredocs-edn.netlify.com?
Aha. I’m currently on a train with no network, so it’s a bit inconvenient that it stops my repl from working. :)
Previously the Grimoire integration was doing http requests on demand, but when we swapped this for ClojureDocs there wasn’t a real API so we cooked this service that generates an EDN export of all data every day from the official json export.
Yeah, we obviously missed this part. 🙂 People behind firewalls were also in for a surprise.
I guess we should try to do something sensible in the absence of internet connection.
@U051BLM8F I also hit this issue today while travelling. It was in a project where everything already worked for a few days before so not sure how many times it tries to update the cache... But it basically made repl experience very poor - no docs showing (for fns at least, Java classes seemed to work), couldn't jump to function definition (`cider-find-var`), etc.