{"version":"2.1.232","anchor":"messaging-socket-separates-post-bind-setup-failures-from-bin","canonical_anchor":"messaging-socket-separates-post-bind-setup-failures-from-bin","heading":"Messaging socket separates post-bind setup failures from bind failures","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/messaging-socket-separates-post-bind-setup-failures-from-bin","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Messaging socket separates post-bind setup failures from bind failures\n\nIf the local messaging socket binds but then fails setup, it cleans up and reports that separately.\n\n**What**\n\nIf the local messaging socket binds successfully but setup then throws, the server releases its held state, runs its cleanup callback, and records the failure cause as post-bind setup, distinct from bind-time failures such as a too-long socket path.\n\n**Evidence**\n\n`post_bind_setup_failed`\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}