fix(galaxy): #872 detail-0 failure rows route on category, not detected_by
Every raw detected_by value names an MXAccess layer (requesting/responding LMX, NMX, automation object); the gateway's own failures arrive as ProtocolStatus. The 'non-zero source = transport failure' rule made a failure the responding object detected a comms error. Item 1 of #872 (Warning/Pending categories) stays open pending a captured row. Claude-Session: https://claude.ai/code/session_01GT67AD99zQQqpLCVm3p7xk
This commit is contained in:
@@ -128,14 +128,12 @@ internal static class StatusCodeMap
|
||||
// generic Bad (#866, a stopped platform's ScanState on VD03), MX_E_InvalidObjectId (8) surfaced as
|
||||
// BadNotConnected, MX_E_Overflow (20) as BadCommunicationError. A failure row is also never Good or
|
||||
// Uncertain, whatever its detail.
|
||||
if (status.Detail != 0) return FromCategory(status, logger);
|
||||
|
||||
// detected_by != Mxaccess (raw_detected_by != the MXAccess source enum) implies
|
||||
// the failure happened pre-call (gateway, worker, transport) — surface as a
|
||||
// communication error rather than a generic Bad.
|
||||
if (status.RawDetectedBy != 0) return BadCommunicationError;
|
||||
|
||||
return Bad;
|
||||
//
|
||||
// Detail 0 routes the same way. It used to become BadCommunicationError whenever raw_detected_by != 0, on
|
||||
// the belief that a non-zero source meant a pre-MXAccess transport failure — but every detected_by value
|
||||
// names an MXAccess layer (0 requesting LMX, 1 responding LMX, 2/3 NMX, 4/5 automation object; the
|
||||
// gateway's own failures arrive as ProtocolStatus, never as a status row), so the category decides (#872).
|
||||
return FromCategory(status, logger);
|
||||
}
|
||||
|
||||
/// <summary>
|
||||
|
||||
Reference in New Issue
Block a user