This didn't work out for me, I don't know why so I have unlocked the solution.

Post the code.

This is still confusing.

Order by US then EU just means show the US orders first. The requirement needs to state to show them ordered by ID, US first then EU.

that what I thought 'order by US then EU sales' was implying.

I also stumbled on this issue...The Description only states "Order by US then EU sales" but the test is looking for ID 1 as the first record. In order to solve this I had to put the "id" in the order by. IMO, if this is part of the criteria for success then it ought to be in the description. Something like "The return order of rows should show the US records first, starting with the lowest id"

fixed.

Then, in my opinion, if the order is important to the solution (which it obviously is) this should be stated in the description of the task. At least as a hint.
The diff isn't really helping finding the source of the problem when the order isn't correct (just too many results to really get a sense of what might be the problem).
Even considering that the order isn't defined when not specified in the statement and that then the source of the error isn't the script but the server itself?!

this is more a suggestion than an actualy issue but as far as I know, no.

The order of the rows seems to be important. My first solution was technically correct, but had the EU sales first and then US sales, which resulted in the solution being wrong. Is there a way to make the tests order-independent?

Dear Karill,

I've posted a question about my solution to this Kata using C#. It is working in VS but not here. Could you help me out please?

Thanks in advance,
Marloes

In your ternary in the else part, you are missing the .reverse().toString() on the StringBuilder instance.

Still, returning a function from within a function, also sometimes known as a delegate (like in C#) is a basic language feature.
8kyu really might be too difficult, but i think it shouldn't be any lower (or is it higher?) then 7kyu too.

Thank you for the code for the header. It seems that it is contained correctly in the discription but while writing my translation, it didn't display correctly in the preview.
We'll see if it works once the translation is accepted (once you can see it, that is).