Loading collection data...
Collections are a way for you to organize kata so that you can create your own training routines. Every collection you create is public and automatically sharable with other warriors. After you have added a few kata to a collection you and others can train on the kata contained within the collection.
Get started now by creating a new collection.
The other kata looks to have been abandoned, so go ahead with yours.
So, are we to leave this as an issue or let it play itself out?
Both are different special cases of the same underlying general problem.
So maybe make a kata for the general problem? (which is basically the same as this, but also allowing for the circles to have different radii (indluding 0))
Yeah, I'm mostly just raising this issue to point this out. It'll need to be eventually resolved in some way.
Looks like you are correct. Could we just wait and see if either even get approved? Mine seems to be closer, but has gone stale. So it may be a non-issue.
So apparently this kata is a duplicate of https://www.codewars.com/kata/5a0511b8697598c8c9000069, despite looking completely different.
Something should be done about this.
I figured as much. I just wasn't sure, because I have yet to identify where I may be accidently creating a huge array. I think I will just restructure my loop.I hit the same issue again after feformatting my loop. But this time the problem was more visible. I had a bug not correctly handing one-word lines.
That is a problem with your code (and the error is a big hint of what is going wrong).
Javascript. Consistently pass everything up until random width 13.
Fatal error in , line 0
Fatal JavaScript invalid size error 169220804
#FailureMessage Object: 0x7ffc047abf40
1: 0xbd7061 [node]
2: 0x1dfa6b4 V8_Fatal(char const*, ...) [node]
3: 0xeeb3a8 [node]
4: 0x10997b2 [node]
5: 0x1099a75 [node]
6: 0x12a813b v8::internal::Runtime_GrowArrayElements(int, unsigned long*, v8::internal::Isolate*) [node]
7: 0x16e99f9 [node]
Marking as resolved, as it will be before I republish.
Yes. I will put this one on ice until I have some time to reformat. Thanks again.
I don't think having an exact solution is an issue. Having only 1 fixed test, however, is definitely an issue.
So at least you'll have to set up a fixed tests, then some random tests with random initial conditions. This will also require the interface to change a bit, as it currently doesn't allow for more than 1 runs.
(Also, beam angular position/velocity and ball position/velocity should be randomized too. The current initial condition is too easy, as you can see)
Thank you for the explanation. Un-published. Do you think it is possible to fix this kata?
This comment is hidden because it contains spoiler information about the solution
Loading more items...