This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # bangalore-clj (1)
- # beginners (60)
- # boot (30)
- # cider (7)
- # cljs-dev (10)
- # cljsrn (2)
- # clojure (163)
- # clojure-conj (10)
- # clojure-france (1)
- # clojure-greece (2)
- # clojure-italy (7)
- # clojure-russia (41)
- # clojure-serbia (22)
- # clojure-spec (41)
- # clojure-uk (41)
- # clojurescript (178)
- # cursive (36)
- # datascript (1)
- # datomic (23)
- # dirac (38)
- # graphql (12)
- # hoplon (20)
- # immutant (32)
- # instaparse (3)
- # keechma (1)
- # lein-figwheel (18)
- # leiningen (8)
- # liberator (1)
- # luminus (30)
- # lumo (29)
- # off-topic (18)
- # om (17)
- # pedestal (7)
- # planck (37)
- # precept (1)
- # re-frame (67)
- # ring-swagger (2)
- # timbre (1)
- # untangled (8)
- # vim (2)
Hi, I am having an issue where I just added a new page using reagent. Locally it appears for an instant and then disappears and when I deploy it, it doesn't appear at all.
I built it very similar to the Web Development with Clojure book, and I am at a bit of a loss as to why this is happening only on a single route of my app.
This is the component causing the issue: https://github.com/achernyak/fcc-tracker/blob/master/src/cljs/fcc_tracker/components/members.cljs And This is where I am routing it: https://github.com/achernyak/fcc-tracker/blob/master/src/cljs/fcc_tracker/core.cljs
I figured out the issue. I was using a destructuring
session/get! to get the table data, which was causing the flicker. By switching it to
session/get it was fixed.
I am trying to deploy on a free instance of heroku but I get the following errors in my logs when i try to run
heroku run lein run migrate. Has anyone been able to get around this?
2017-06-21T13:28:46.063924+00:00 app[api]: Starting process with command `lein run migrate` 2017-06-21T13:28:52.692937+00:00 heroku[run.1423]: State changed from starting to up 2017-06-21T13:28:52.595667+00:00 heroku[run.1423]: Awaiting client 2017-06-21T13:28:52.618633+00:00 heroku[run.1423]: Starting process with command `lein run migrate` 2017-06-21T13:29:33.790220+00:00 heroku[run.1423]: Process running mem=896M(174.0%) 2017-06-21T13:29:33.790220+00:00 heroku[run.1423]: Error R14 (Memory quota exceeded) 2017-06-21T13:29:53.425823+00:00 heroku[run.1423]: Process running mem=994M(194.2%) 2017-06-21T13:29:53.425924+00:00 heroku[run.1423]: Error R14 (Memory quota exceeded) 2017-06-21T13:30:13.758884+00:00 heroku[run.1423]: Process running mem=1076M(209.2%) 2017-06-21T13:30:13.759003+00:00 heroku[run.1423]: Error R15 (Memory quota vastly exceeded) 2017-06-21T13:30:13.759111+00:00 heroku[run.1423]: Stopping process with SIGKILL 2017-06-21T13:30:16.996720+00:00 heroku[run.1423]: State changed from up to complete 2017-06-21T13:30:16.984168+00:00 heroku[run.1423]: Process exited with status 137
Once I have it figured out I will add it to the heroku deploy docs. Because right now they recommend what I was trying.
@yogthos in relation to the earlier error, I found out that immuntant only depends on
webjars-locator-jboss-vfs for wildfly support from the #immutant channel. Why does luminus use it?
@yogthos That's what @tcrawley told me. I did manage to figure out what dependency was causing the issue.
webjars-locator-jboss-vfs wanted a newer version of
ring-webjars did, and apparently the way boot handled that caused the issue. When I excluded
ring-webjars the above issue went away. However I'm now getting a new issue
Whenever I try and run the project it starts us normally, the the nrepl server immediately stops and the program proceeds to close down without any error message. The only thing out of the normal is this message:
org.projectodd.wunderboss.WunderBoss - Returning existing component for org.projectodd.wunderboss.web.Web:-1645144552, ignoring options.
does lein run pass any args to
-main? I don't have boot set up to do that, so that could be an issue
Looks like the same message was appearing here: https://github.com/luminus-framework/luminus-template/issues/214, though with different cirumstances and results. I'm not sure if it's related
but I'm using a default project from a template, so their shouldn't be any environment variables set, right?
.lein-env is used to track profile generated config, however that should be empty if you're not using a database
BTW, I have the project on github for sharing/testing purposes if you want to inspect my setup https://github.com/DonyorM/luminus-boot