fixed there

I upgraded Ruby to 3.0 + RSpec assertions

this was fixed there

C++ translation should get rid of using namespace std;

I will try to get someone to take a look into DB, maybe it's a problem with some data consistency.

Merged.

i do not think so, according to the reply i linked. what is peculiar is that I am pretty sure it's the first time ever I see this banner, it must be a really rare bug that is perhaps unique to this kata, or almost so

Does this happen also when applying changes with a fork?

C fork (author inactive)

• moving the testing code out of preloaded

publishing changes from the editor in this kata fails with a red banner "Revisions is invalid"... searching the web for "revisions is invalid" codewars yields a single result, which is a reply to this comment in this Discourse, really peculiar

Fixed the warning.

Exit code 132 is due to Swift crashing with *** Program crashed: Illegal instruction at 0x000055cd112cc93c ***. "Illegal instruction" in Swift are caused by failed preconditions, such as integer overflow or out-of-bounds accesses.

This one is caused by integer overflow in your while (c != 0) loop. You reverse the digits of c into m by successive multiplications of m by 10 and adding the last digit of c. This fails when c has as many digits as Int.max and ends with large digits, the last multiplication by 10 overflows.

I added better assertion messages to Swift.

(C++) this warning must have been cleared at some point, it is not reproducible

i fixed everything. the input array is now const-qualified. the tests do not alter it. it is printed upon failure. no more UB in the test suite. there is still a reference solution though, because i found it easier than generating the array from the answer.