{"version":"2.1.239","anchor":"plugin-eval-scanning-no-longer-follows-symlink-loops-or-auto","canonical_anchor":"plugin-eval-scanning-no-longer-follows-symlink-loops-or-auto","heading":"Plugin eval scanning no longer follows symlink loops or automounts","tier":"notice","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/plugin-eval-scanning-no-longer-follows-symlink-loops-or-auto","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### Plugin eval scanning no longer follows symlink loops or automounts\n\nPlugin eval scanning no longer hangs on symlink loops or automounted directories.\n\n**What**\n\nThe directory walk that collects plugin eval cases now tracks the real paths of parent directories and refuses to follow a link back into the directory under test or into any directory already on the current path, so a symlink cycle can no longer hang or duplicate the scan.\n\n**Details**\n\n- Automounter map directories are skipped, because listing them would trigger a reach out to network hosts.\n- A global cap on directories visited and a per-path depth cut bound the walk.\n- Entries that cannot be examined are reported instead of being skipped in silence.\n\n**Evidence**\n\n`links back into a directory on the current route`\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}