Broken symlinks in plugin eval suites now raise a named error instead of looking like empty directories.
What's wrong with this entry?
A case file, a graders/ directory, a plugins entry or an eval suite root reached through a symlink whose target does not exist now raises a named error instead of being silently treated as missing. A suite directory that links to its own parent or higher is refused, and a directory that cannot be read reports the underlying system error rather than looking empty.
- Example message:
graders/: dangling symbolic link.
graders/: dangling symbolic link
Strings lifted out of the shipped bundle, so the claim above can be checked against them.