Ab.Transport: RequestScheduler fragment/lock follow-ups #567
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?
Context: native .NET Allen-Bradley transport work (plan
docs/plans/2026-10-07-native-ab-transport.md, branchfeat/native-ab-transport, not yet merged). Parked as a Minor during per-task review — none of these block the plan.RequestScheduler(MSP coalescing + fragmented reads/writes) follow-ups:lock(this)on the privatePendingtype — switch to a private lock object.Fixed: private lock object; struct handle compared across Read Tag Fragmented fragments (mismatch fails BadReply). Residual: wide-struct fragmented WRITE unproven on a real controller (presses are read-only, no bench controller) — recorded in docs/drivers/AbCip.md. (merge
bd2bebedon master, pushed 2026-10-08)