Number of random tests is increased to 1001 to ensure all cases get tested. And your other issue also is fixed https://www.codewars.com/kumite/6830931d9b22cae2fe115973?sel=6830931d9b22cae2fe115973

Fork that updates the initial code with a comment showing the definition of RGB.

done

Done in this fork

I've made a translation that modifies the description to address this.

IIUC there is no right answer for this.

I don't know if the description got more specific in the meantime, but I was also curious so I already checked... 420690045 is not a multiple of 45, so it's definitely a "crazy value". -420690045 % 45 == -30, and -420690045 % 360 == -165 doesn't match any direction.

Yours and the solutions that match your results are probably rounding off, turning -165 (-45 * 3.66...) to -135 (-45 * 3) with integer division or some equivalent, somewhere.

I don't think this is an Issue, since the solution to any kata can be found on the Internet.

When kata authoring is done right, you have a unique problem. Neither the internet nor an AI will know what to do with your kata.

Ruby fixed in this fork, other languages still pending fixes.

Non-array tests (input validation) no longer required.

Fixed, thanks

What is wrong with free text parsing problems? (in general)

Assets should be a superset of both equities and currencies. I think the problems are the places in the descriptions where assets and equities are used interchangably.

Edit: Or, since he seems to want separate imports for these different asset classes, he should specify the asset types in the argument, like you suggest.

Second Edit: On third thought, I think get_shift arguments are named just fine, but asset_import should either handle all types of assets or be renamed to equity_import but also include in its name evidence that we're importing historical data and not data regarding the users holdings.

Hi Voile, I've added a random rotation to increase the number of permutations, but its difficult to generate tests on the fly for this. Generating a puzzle that has a guaranteed single solution can take considerably longer than solving the problem, and it could add inconsistent timeouts to the problem.