name: A path the tool cannot even stat is skipped, and the run continues
why: The third specification change established that an unreadable file is reported rather than raised, because a formatter given twenty files must not decline to format nineteen. That fix wrapped the read; it did not wrap the three stat calls before it, so a path too long for the filesystem still escaped through a traceback with empty stdout and abandoned every other path in the run. A path that cannot be stat'd cannot be shown to be a regular file, so it is out of scope the way a missing path is -- skipped silently, no error, and the file named beside it is still formatted. Reporting it instead was the alternative, and it was declined because the tool cannot tell an over-long name from a name that merely does not exist.
argv: --write --json aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa.md note.md
exit_code: 0
