Update1: apparently asserts do not trigger on the server (good to know for the future), I’ve updated this question and to reflect that. However, when I made checks without depending on asserts I found really bad things. New findings is in a separate question: https://discuss.codechef.com/questions/137657/oct18-challenge-cheftaks-testcases-are-completely-broken
(below is mostly the same with a few removals)
Bad/not updated description
The description still has issues with how it defines the input data (it calls things integers that are not integers in the data). The actual format of the data on the server is weird. I had to waste a few attempts to see that it differs from what we expect from a multi test-case problem.
Checker accepts clearly invalid input
The criterion for WA or not does not seem to be enforced at all. Mostly ignoring the input and just printing the correct number of zeroes gives a correct answer with score 0, fair enough. But if we instead print 1 all the time this also gives correct with score one. That answer could have been valid in super specific test cases, but printing clearly invalid things like all -1 or 100000000 also gives correct and score 0. Obviously there are errors in the checker.
