This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-05-17
Channels
- # announcements (10)
- # aws (10)
- # babashka (11)
- # beginners (77)
- # calva (9)
- # cider (10)
- # cljdoc (7)
- # cljs-dev (47)
- # clojure (47)
- # clojure-uk (4)
- # clojurescript (87)
- # community-development (15)
- # conjure (14)
- # core-async (25)
- # cursive (6)
- # fulcro (6)
- # helix (3)
- # joker (2)
- # nrepl (1)
- # off-topic (1)
- # pathom (9)
- # pedestal (6)
- # re-frame (22)
- # reitit (15)
- # shadow-cljs (26)
- # spacemacs (16)
- # testing (2)
- # tools-deps (12)
- # uncomplicate (10)
- # xtdb (22)
I am using cognitect's aws api, and creating an api client with (aws/client {:api :s3 ...})
, for some reason it gets stuck when called from a namespace on repl init (i.e. I add (def x (aws/client ...))
call to the namespace which is marked as init-ns
in my project.clj
, run lein repl
and it hangs), but works if I comment it out in the namespace and run (def x (aws/client ...))
inside the repl after the repl has started up. In the repl it works quickly, certainly in under a second, I've tried larger repl timeout than the default 30s, it doesn't help. Any ideas what could be the cause of this?
clients are not designed to be def'fed top-level. wrap it in a delay
if you really need it top-level
Ok, thanks! Out of curiosity, what's the difference between when it is top-level vs when it is not? What breaks? I assumed that writing lines in the repl is the same as basically appending the lines to the namespace repl is in.
in the REPL for exploration I think it's fine, yes it's similar to top-level in a namespace