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.
nope, only the contests ;)
bah, it was a problem with using numpy, needed to convert the numpy array back to list...
Got an eval error with Python 2 - seems that the verifier tries to compare array to array and it fails. The same problem occure with the sample test and resolved when compared htmlized: htmlize(resp) == htmlize(end)
Time: 580ms Passed: 1 Failed: 0 Exit Code: 1
Test Results:
Glider
▓▓░░░░
░░▓▓▓▓
▓▓▓▓░░
Glider 0
STDERR
Traceback (most recent call last):
File "main.py", line 38, in
test_function(get_generation(gliders[0], 1), gliders[1])
File "main.py", line 12, in test_function
test.expect(actual == expected, 'Got <:LF:>' + htmlize(actual) + '<:LF:> instead of <:LF:>' + htmlize(expected))
ValueError: The truth value of an array with more than one element is ambiguous. Use a.any() or a.all()
Also there are multiple accepted solution with at_bats > 100 ( not with gte )
These should not be accepted.
Nice Kata, but yet after optimizing it was running to timeout twice before accepted (with 9 seconds run time)...
Thanks for your suggestion, worked like a charm!
It's not a 5 kyu Kata, 7 or 6 kyu maximum...
Also, truncate to day, but still need to keep as datetime seems lame.
Can't site admins do anything about it?
Kata should be deleted as it can't be completed at all anymore.
I have created a github (system) issue - I hope these kind of issues will be possible to be fixed.
I could not solve it, the issue is with the test.
improper solution, should be invalidated
Probably we have a test error:
SEQUEL DEPRECATION WARNING: Calling a dataset filtering method with a plain string is deprecated and will be removed in Sequel 5. Use Sequel.lit("age > 50") to create a literal string and pass that to the dataset filtering method, or use the auto_literal_strings extension.
I had the same issue, probably the built in function calculates with a constant that is different - binarily - from 1/3.
This comment is hidden because it contains spoiler information about the solution
This comment is hidden because it contains spoiler information about the solution
Could only finish the KATA with a 'nice' hack on the last test case :(
Loading more items...