{"version":"2.1.239","anchor":"broken-symlinks-in-plugin-eval-suites-now-report-an-error","canonical_anchor":"broken-symlinks-in-plugin-eval-suites-now-report-an-error","heading":"Broken symlinks in plugin eval suites now report an error","tier":"notice","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/broken-symlinks-in-plugin-eval-suites-now-report-an-error","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### Broken symlinks in plugin eval suites now report an error\n\nBroken symlinks in plugin eval suites now raise a named error instead of looking like empty directories.\n\n**What**\n\nA 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.\n\n**Details**\n\n- Example message: `graders\/: dangling symbolic link`.\n\n**Evidence**\n\n`graders\/: dangling symbolic link`\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}