{"version":"2.1.228","anchor":"ancestor-process-checks-no-longer-read-a-failed-lookup-as-a-","canonical_anchor":"ancestor-process-checks-no-longer-read-a-failed-lookup-as-a-","heading":"Ancestor process checks no longer read a failed lookup as a no","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228\/e\/ancestor-process-checks-no-longer-read-a-failed-lookup-as-a-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228","markdown":"### Ancestor process checks no longer read a failed lookup as a no\n\nA failed process lookup is no longer mistaken for a confirmed no when checking parent processes.\n\n**What**\n\nDeciding whether a given process is an ancestor of this one now returns three states instead of true\/false, so a lookup that produced no usable information is distinguished from one that positively ruled the process out.\n\n**Details**\n\n- The result is only cached when the process start token read before and after walking the ancestor chain matches.\n- The shell command that walks the parent chain now emits explicit END and FAIL sentinels, so a truncated or failed walk is reported instead of being treated as an empty chain.\n\n**Evidence**\n\n`no-evidence`\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}