{"version":"2.1.222","anchor":"remote-io-warns-when-the-drop-sender-notice-cannot-be-writte","canonical_anchor":"remote-io-warns-when-the-drop-sender-notice-cannot-be-writte","heading":"Remote-io warns when the drop sender notice cannot be written","tier":"internal","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.222\/e\/remote-io-warns-when-the-drop-sender-notice-cannot-be-writte","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.222","markdown":"### Remote-io warns when the drop sender notice cannot be written\n\nA failed remote notice write now logs a warning instead of disappearing silently.\n\n**What**\n\nThe remote-io transport writes an attestation drop notice through the CCR client and now logs a warning if that write fails, rather than dropping the failure silently.\n\n**Details**\n\n- New handler on the transport; the warning text is \"[remote-io] drop sender-notice write failed\".\n\n**Evidence**\n\n`[remote-io] drop sender-notice write failed`\n\n- Area: Remote Control\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}