{"version":"2.1.248","anchor":"directory-sync-plumbing-for-install-holds-has-no-caller-and-","canonical_anchor":"directory-sync-plumbing-for-install-holds-has-no-caller-and-","heading":"Directory-sync plumbing for install holds has no caller and no implementation","tier":"soon","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/directory-sync-plumbing-for-install-holds-has-no-caller-and-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Directory-sync plumbing for install holds has no caller and no implementation\n\nDirectory sync gained hold and release install methods with no caller or implementation.\n\n**What**\n\nThe directory-sync wrapper gained six methods, and two of them, `holdInstalls` and `releaseInstalls`, are neither called from anywhere in this build nor implemented by any sync engine in it. The wrapper does keep real state for them (a pending set of held installs), so this is groundwork for something not yet shipped.\n\n**Details**\n\n- `onOffline` has exactly one caller, the cloud file-sync offline notice.\n- `catchUp`, `syncPoint` and `capturePoint` are implemented by the real engine and reported in telemetry, but nothing outside the wrapper invokes them.\n- The wrapper now returns a \"not running\" shape instead of undefined when no engine is open.\n\n**Evidence**\n\n`releaseInstalls: (e) => {`\n\n- Area: Cloud Sessions\n- Tier: Nothing to try yet\n- Useful: 1\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}