Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Residuals from the 2026-10-08 sweep that need no hardware.
Sources: closing comments on #565, #570, #579; docs/drivers/AbCip.md (lease release); docs/plans/2026-10-07-native-ab-transport-gate-results.md.
ConnectionLease.ReleaseInBackgroundagainst ab_server (today only the 25-cycle offlineNativeAbCipLeaseReleaseTests)EncapsulationClientwrite-timeout fault path (needs a peer that stops reading with full socket buffers — e.g. a stream seam)ErrorBadParam) still backs the whole device off — align with native's per-tagBadConfigurationError, no backoffFiled 2026-10-08 by the pending/deferred-work sweep after the #562–#591 issue sweep.
Resolved on master (merge
6a5e804e, plus36343c12andcb838d4a).NativeLeaseReleaseSoakTests(AbCip.IntegrationTests) against ab_server controllogix (7e368425). Ran 200 cycles, passed (3m19s); budget now scales withAB_LEASE_SOAK_CYCLES(cb838d4a) because a fixed 120 s timed out above ~100 cycles.A_blocked_write_times_out_faults_the_session_and_leaves_no_unobserved_exceptioninEncapsulationClientTestsvia a blocking-stream seam (21267750).ErrorBadParam: at tag create it is now a per-tag config error with no device backoff, aligned with native (6a6ac9a1,LibplctagStatusTranslation); a BadParam on a live handle is deliberately not treated as a name problem.AbLegacyUnsupportedPathTests(b37e9613); the native write refusals are now decided before any wire traffic, for status-bit sub-elements of any type and PLC-5 (e863e9f0, merge36343c12). Ran against ab_server plc5 + slc500 (AB_SERVER_ALLOW_WRITES=1): AbLegacy integration 13/13.Closed 2026-10-08 by the hardware-available issue sweep (master
d898262c).