The listed languages do not comply with the rule from the description:

Note: despite its name in some languages, your function should handle any Unicode codepoint:

1. Go has no Unicode tests
2. Factor has no Unicode tests
3. In JavaScript, Unicode is represented by a limited set of Braille
4. In Ruby, Unicode is represented by a limited set of Braille
5. In Rust, Unicode is represented by a limited set of Braille
6. In Python, Unicode is represented by a limited set of Braille
7. In Lua, Unicode is represented by a limited set of Braille, but there are several fixed tests with emoji

Some of these issues have been mentioned before, but they haven't been fixed, so I'm raising them again.
Most translations use Braille characters as Unicode tests. This is likely because the translations were done from Python and thus inherited its Unicode test suite. N stated below that the lack of random Unicode tests for Python isn't a big problem, but that's not true. Python is the most common language on CodeWars, and the likelihood that translations into other programming languages will be done from Python is very high, so the Python version should be flawless and serve as a kind of gold standard.

now on dart Translation Dart

For C# the opening and closing braces of the class should be at the line start.

Typo in the description in "The digits are sequential, incementing†: 1234" : "incementing" instead of "incrementing".

According to the description exactly as stated, if you put a 2-digit number in awesome_phrases (like 69) then it should not signal when reaching this number. Is that the expected behavior? Or should awesome_phrases be an exception to the 3-digit mileage rule?

can someone please explain, how i should get another 2 element from test for knowing out is there any interesting number?

Not all languages (eg Python) test for Unicode-only characters, and instead only test for Ascii.

JS, maybe others:
Literally a single random test. Just the one.

WTF?
expected 'G' to equal ','

I want to see the test case that fails! I don't know what to fix! :(

suggested edge cases that a first version of my code did not handle correctly, but passed anyways:

• trailing empty column:
  • "1,2,,\n3,4" --> [ [ '1', '2', '', '' ], [ '3', '4' ] ]
  • "1,2,," --> [ ['1', '2', '', ''] ]
• trailing empty row:
  • "a,b,c\n" --> [ ['a', 'b', 'c'], [''] ]
  • "\n\n\n" --> [ [''], [''], [''], [''] ]

Python (at least):

Random Tests are not guaranteed to fail a faulty solution such as this one that fails to account for upper / lowercase counting as the same char, as shown the 3 test cases below.

input  ' iwDwW59viI;LMxADnEc5XMCVVrX3hp0u '
result 'W' should equal '9'

input  'f.FGP1.H59u n3'
result 'F' should equal 'G'

input  'peLiEWOfbS,Brl1PsUcBgmaRnMShh5q8osKoyziKTvjv'
result 'E' should equal 'W'

What's meen testUpcomingBigNumbers
It's last crash test, and i don't understand how will make correctly

• JS Node 18. should be enabled

• decodeURIComponent function is not mentioned anywhere