This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-04-08
Channels
- # admin-announcements (7)
- # aws (5)
- # beginners (37)
- # boot (39)
- # cider (4)
- # clara (2)
- # cljs-dev (32)
- # cljsjs (1)
- # cljsrn (12)
- # clojure (235)
- # clojure-austin (3)
- # clojure-belgium (7)
- # clojure-berlin (11)
- # clojure-dev (36)
- # clojure-france (10)
- # clojure-japan (10)
- # clojure-poland (2)
- # clojure-russia (39)
- # clojure-uk (4)
- # clojurescript (81)
- # code-reviews (9)
- # core-async (6)
- # core-logic (1)
- # datomic (32)
- # editors (7)
- # emacs (1)
- # hoplon (191)
- # jobs-discuss (14)
- # juxt (4)
- # lein-figwheel (4)
- # leiningen (3)
- # off-topic (7)
- # om (49)
- # onyx (34)
- # other-lisps (1)
- # overtone (11)
- # parinfer (1)
- # proton (5)
- # re-frame (11)
- # reagent (12)
- # spacemacs (2)
- # untangled (90)
- # yada (15)
1.1.5 is working for me now. Don't know what happened, except possibly that before I wasn't explicitly requiring bidi
...
When I upgrade to this release, my stuart sierra component system which is started from the leiningen main run returns after starting the system
(defn hello-world-handler
[req]
{:status 200
:headers {"content-type" "text/plain"}
:body "hello world!"})
(defn -main
[& args]
(http/start-server hello-world-handler {:port 10000}))
ok. it is probably because of this https://github.com/ztellman/aleph/commit/9b4504b61ff5ab2128c8fc3014fc8c2b63d55a5e
and the fact that I don't have any other non-daemon threads running in my application, hence the JVM exits.
that took me almost an entire day to go from 'why the hell does kubernetes kill my container?' > 'shit, docker locally also does this' > 'man, my uberjar build must be wrong' > 'wait, lein run doesn't work either?'
included upgrading the cluster because of some totally unrelated thing in /var/log/messages that was mentioned somewhere in a docker issue
@stijn that sounds frustrating! you need to reverse your debug process ;)