You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .agents/sow/current/SOW-0021-20260613-netipc-at-scale.md
+7Lines changed: 7 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1037,6 +1037,13 @@ Tests or equivalent validation:
1037
1037
- C Windows now validates the same no-progress `PAYLOAD_EXCEEDED` rejection for APPS_LOOKUP and CGROUPS_LOOKUP.
1038
1038
- Go POSIX/Windows, Rust POSIX/Windows, and C POSIX/Windows validate logical response-byte ceilings for APPS_LOOKUP and CGROUPS_LOOKUP.
1039
1039
- C POSIX also validates a final stitched response-buffer allocation fault; Go and Rust use explicit logical response-byte ceilings as the deterministic memory-pressure simulation available in those test harnesses.
1040
+
- Large response split/stitch suffix-reservation validation:
1041
+
- Added C, Rust, and Go POSIX/Windows tests where one logical APPS_LOOKUP or CGROUPS_LOOKUP request receives large labeled known items that cannot fit in one response payload, requiring transparent `PAYLOAD_EXCEEDED` suffix retries and final response stitching.
1042
+
- The first C POSIX fail-first run exposed a real builder gap: lookup builders could accept one more full known item and then have too little buffer left to encode `PAYLOAD_EXCEEDED` for the remaining suffix. The fix reserves space for the compact overflow suffix before committing another full item.
1043
+
- C protocol/server dispatch now provides per-request compact suffix item lengths to APPS_LOOKUP and CGROUPS_LOOKUP builders; Go and Rust use the same reservation model in both protocol dispatch helpers and raw service dispatchers.
0 commit comments