{"version":"2.1.247","anchor":"messaging-socket-path-now-errors-instead-of-silently-doing-n","canonical_anchor":"messaging-socket-path-now-errors-instead-of-silently-doing-n","heading":"--messaging-socket-path now errors instead of silently doing nothing","tier":"use","area":"IPC","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/messaging-socket-path-now-errors-instead-of-silently-doing-n","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### `--messaging-socket-path` now errors instead of silently doing nothing\n\nA bad messaging socket path now fails with a clear error instead of being silently ignored.\n\n**What**\n\nPassing an unusable socket path used to be logged and ignored. It now fails with a user-facing error naming the flag, spelling out what was rejected: a remote or UNC path, or a pipe name with extra segments or a trailing dot or space.\n\n**Details**\n\n- The refusal is recorded as a start-failure cause `path_refused`; when the path did not come from the flag explicitly, it is recorded without throwing.\n- Storage is now threaded through peer sends and shutdown, so peer notices and hold receipts carry it.\n\n**Evidence**\n\n`not a usable local socket address (a remote\/UNC path, or a pipe name with extra segments or a trailing dot\/space)`\n\n- Area: IPC\n- Names: `--messaging-socket-path`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 1\/5"}