3 ms·
Assuming you entered it in the format we take it in right now (separated out, etc), it's just very possible that we're hanging on the backend. We aren't able to
by Klonoar 16y ago
Assuming you entered it in the format we take it in right now (separated out, etc), it's just very possible that we're hanging on the backend. We aren't able to touch the thing for a week while it's being judged, so we've had to periodically kill off things to keep it alive.
It's not our desire either, but give us time to deal with it and we'll show you some rockin' stuff. ;)
- endtime 16y agoThe first time it timed out. After I posted that I tried again and it let me create the job and then start it...but then the results were the empty object. This made me think I screwed up my JS, but it's pretty simple and I did test each function individually, so I think it's correct. Anyway, looking forward to you guys getting the kinks ironed out. Very cool idea.
- Klonoar 16y agoYeah, your problem just hasn't run yet, it would seem. We didn't have time to implement running multiple problems at once - currently they enter a queue and wait in line for their turn to get distributed. :( Glad to know you at least got it in there, though!