common_creative
Woops haha meant to search what I said last š
@tedhogan: I'm thinking about using Phoenix, Om, Datomic... looking into if they will fit together
@grounded_sage: may be http://joxa.org/ or http://lfe.io/
if you mean Erlang VM by BEAM
Hi guys, I am currently playing a bit with the 4clojure problems and stumbled upon something that works fine in my repl but the website gives me an Error:
An Error occured: timeout
would anyone take a look at it? I donāt want to post answers to that openly if not asked for...@meikemertsch: I would assume that's just JavaScript timing out. Either your computer is slow or your solution is. I would typically assume it's your solution (don't worry, it happens!), but it could be something else. I actually don't remember how 4clojure works technically. Does it timeout when evaluating something client side?
Or do you submit the answer and you get a timeout error? If that's the case could it be something on their side or your network?
the latterā¦ I have no clue
Itās not something very calculation heavy
happens already on the first one
Ah. So you don't get specifically the timeout error if the solution is different? For example if you just try having the solution be some simple function application such as (+ 1 1)
you don't get the timeout error?
Or is there an infinite loop in your solution perhaps?
@ian why would it work in my repl then?
Oh hm, you said it worked in the REPL.
exactly
That is interesting. Did you try some bogus no-op solution?
I wonder if that stuff is parsed somehow on 4clojure
I just donāt see the issue.
In my repl:
"Elapsed time: 1.419835 msecsā
itās really small
Hm.
Sorry to repeat myself, but the bogus answer? Does any and every solution give the timeout error?
nope
if thereās something wrong the tests fail
But if the solution is right you get a timeout error?
Then surely there is a problem with 4clojure?
I donāt know
Yeah, it timed out for me as well. It must be a temporary problem with 4clojure.
Unfortunately
hmmmm
Thanks Ian
@meikemertsch: That's usually an indication that your solution needs to be optimized. It can be "correct", but not optimized enough to run in the time constraints. It's happened to me too :simple_smile:
Whoops, I see that you're already answered. My slack just did not refresh yet.
Well, I did exchange my āiterateā in my solution by a loop/recur with the rest of the code being the same and it worked...