Looks like it's been fixed, if you open the Custom Testcase, it's formatted properly. However, as pointed out in this post, some of the actual test cases have 4 spaces instead of tabs. Is it an edge case that was missed, or is the problem not stated fully?
@vishal51 I agree. This is one of the stupidest test cases. For example: input: "dir\n........file.txt" (sorry markdown doesn't allow multiple spaces so each dot is a space), is supposedly meant to test whether we handle having spaces in the filename because the expected output is 16, not 12. Only four of the 8 spaces in the second line are meant to indicate that file.txt is a child of dir and the rest is meant to have filename "....file.txt". Seriously?