This is not a kata; a complete solution is already provided in initial code, while the actual tests prints text to the console instead of using the testing framework.

Please review kata authoring guide on how to set up a kata.

I'll have to bite: this kata is effectively just asking to calculate determinants without Laplace expansion.

Besides the fact that it's not very novel, the fact that you have to ban all modules (besides things like math. Yes, fractions is banned too for some reasons) means that Python is not the language you want to write this kata in.

Write the kata in a language more suitable for what you want, like JS or C++. Don't cripple the runtime with ridiculous hacks instead just to barely achieve the same thing. Module blockers are only used because certain Python users aren't willing to learn another language to write their katas in; they aren't supposed to be supported, and when it breaks in the future, someone will have to maintain it (which clearly won't be you, as you don't appear to know how it works, or that it has a glaring flaw as it currently stands).

Doing only the input validation and nothing else passes the actual tests.

So... WTF? Am I just doing a kata about input validation and nothing else? The real tests should contain at least the entire sample tests to ensure solutions must pass the sample tests first.

Also, sample tests are outdated: they still assume index starts at 1.

Return "Unicode number out of range!" if the number is out of parameters of the last number of the unicode table

You never specified what is the magic number you use for this criteria. The maximum theoretical size of the table is 1114112, but the number can be lower in different ways depending on how to account for certain Unicode characters.

And anyways, incorrect checking will pass the kata.

This is just a bunch of existing trivial katas mixed together to not look like a dup. This can barely be called novel.

Also, is there any need to add so many input validations? What do they add to the task? They are considerably more complicated than the actual task itself.

Description does not restrict the range of dates in history. Technically they can be further than current (for example, if users change their system clock), and in this case it's undefined how they should be handled.

Random tests pass in strings in current instead of datetime, which is inconsistent to the sample tests.

If sorted by date/time, return a dictionary containing keys that are "Today", "Yesterday", "This Week", "This Month", "This Year", and "Past a Year" (if there are entries within these time periods) and corresponding values that contain a list of entries within these time periods (sorted by date and time)

Sample tests do not have a test case that demonstrates value besides This Year and Past a Year. Random tests only sometimes go up to This Month. The test coverage is inadequate.

A related issue: there should be fixed tests in actual test code too. It should be a superset of the sample tests.

And anyways, this kata is a duplicate of https://www.codewars.com/kata/60e4dfc1dc28e70049e2cb9d

Your test code is completely broken:

error[E0428]: the name `test1` is defined multiple times
  --> src/lib.rs:26:5
   |
19 |     fn test1() {
   |     ---------- previous definition of the value `test1` here
...
26 |     fn test1() {
   |     ^^^^^^^^^^ `test1` redefined here
   |
   = note: `test1` must be defined only once in the value namespace of this module

error[E0412]: cannot find type `string` in this scope
 --> src/lib.rs:1:25
  |
1 | pub fn max_depth(input: string) -> u8 {
  |                         ^^^^^^ help: a struct with a similar name exists (notice the capitalization): `String`

error[E0425]: cannot find value `output` in this scope
  --> src/lib.rs:29:38
   |
29 |         assert_eq!(max_depth(input), output);
   |                                      ^^^^^^ help: a local variable with a similar name exists: `outpu`

Some errors have detailed explanations: E0412, E0425, E0428.
For more information about an error, try `rustc --explain E0412`.
error: could not compile `challenge` due to 3 previous errors


NOTE: Line numbers in error messages can be incorrect due to concatenation.

There are no sample tests.

There's a dummy JS language version. You need to delete it from the editor.

And anyways, basic pathfinding has been done on many existing katas. So there are no chance yet another one of these will pass beta.

There are no random tests.

The grid is an infinite 2D plane where each cell is either an open space ('.'), an obstacle ('#'), or an exit ('E').

But the input area is clearly finite, and it's not defined what the cells outside the input area is. It looks like everything not included in the input are obstacles?