{"version":"2.1.281","anchor":"o-nofollow-any-probe-caches-a-result-on-any-error","canonical_anchor":"o-nofollow-any-probe-caches-a-result-on-any-error","heading":"O_NOFOLLOW_ANY probe caches a result on any error","tier":"internal","area":"File Access","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/o-nofollow-any-probe-caches-a-result-on-any-error","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### O_NOFOLLOW_ANY probe caches a result on any error\n\nThe noFollowAny capability check now always saves a result, counting any error other than EINVAL as working\n\n**What**\n\nClaude Code tests whether the system supports `O_NOFOLLOW_ANY`, an option for opening files. It records the answer as `noFollowAny`. The answer is now always saved:\n\n- `EINVAL` error: recorded as \"rejected\"\n\n- any other error: recorded as \"works\"\n\nBefore, only `EINVAL` saved an answer, and any other error left it blank.\n\n**Why**\n\nThe check now always ends with a stored answer, where before it could be left empty after an unexpected error.\n\n- Area: File Access\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}