And also can do height ** 2, pow(height) <--- (for this you need importing pow from math or importing math)

The "The challenge here is to modify the provided string" in description, and "Modify the string s" in solution setup, are confusing because it's either technically incorrect, or can be interpreted differently, depending on whether s is a mutable or an immutable string.

can a mod take this kata out of draft then: https://www.codewars.com/kata/5c45e3b0a4db1e0922ddcad0/discuss#65438b60da59f62f8be552e6

FYI, the behavior got changed: https://github.com/codewars/codewars.com/issues/3103#issuecomment-1846521123

"Unpublish on two issues" kicks in only on relatively new kata. Additionally, mods should be able to publish drafts if something gets lost, but they need a direct link (note: mods are still not able to un-retire autoretired kata).

Closing to test something. Will re-raise if needed.

the two most recent situations I could trace, first one might be another issue as it got retired instead of being sent back to draft:

• https://www.codewars.com/kata/654adab313799a22c0442b37/discuss#654be487234c0da38c44bd4b
• https://www.codewars.com/kata/5c45e3b0a4db1e0922ddcad0/discuss#65438b60da59f62f8be552e6

I think it's basically the business model and amount of resources available to tackle such issues. I believe there is only 1 dev working on CW.

Sorry for intruding into this convo but is there a reason why Codewars still keeps these weird mechanics? Every docs page is basically some variant of "due to the unfortunate inconvenient way of doing X, do Y instead." I've only been active on this site very relatively recently and some weird mechanics choices have been obvious since day 1.

Very nice suggestion especially regarding the second one, this can prevent occurrence of beta katas with worthwhile quality and novelty being sent back to draft and left to die there ^^

Awaiting other PU's response in this thread ~

it should be easy, if an author is NO LONGER ACTIVE, either ...

• 1. NEVER put a beta kata back to DRAFT, in order for the ACTIVE beta community to handle errors instead of the author
• 2. allow not just the author, but also ANY user with sufficient honour to be able to REPUBLISH beta kata's that are sent back to draft

I've raised the issue in Discord, hoping for a reasonable explanation or else this seems like some unexpected behaviour thanks to the (>= 2 issue sending kata back to draft mechanism) :(

I've seen several beta's get nuked like this the past few weeks. Always high satisfaction rating, always inactive author, always someone edits/forks/approves, and BAM! to draft and to oblivion

lmaooooooooooo, all those efforts are down to the drain now..............

Great! this approval made the kata go back to draft (thank you CW). Author is not active, so bye bye kata

done in latest fork of yours