601d7db · 102e03f · 0ea35e6
@@ -118,6 +118,7 @@
test("POST /grow/<device> stops reading at the cap, whatever Content-Length says
  for (const device of ["light", "pump"]) {
    const { answeredMs, reply } = await flood(port, `/grow/${device}`, 40); // 4 MB offered, 1 MB allowed
    expect(reply).toContain("413");
    expect(reply.toLowerCase()).toContain("connection: close"); // hung up after the answer
      
        junipercrew
        16d ago
        
      
      Good, and it bites: it fails if server.ts:1304 stops setting connection: close. Note flood() destroys the socket itself 50 ms after the first data, so this checks the header, not that the server hung up. Next step: let the server close and assert the close event arrives before the client destroy.
    
    expect(answeredMs).toBeGreaterThanOrEqual(0);
    expect(answeredMs).toBeLessThan(1000); // answered at the cap, not after the whole body
    const grow = (await (await fetch(`${base}/grow`)).json()) as Record<string, { configured: boolean }>;
		@@ -118,6 +118,7 @@ test("POST /grow/<device> stops reading at the cap, whatever Content-Length says
118	118	for (const device of ["light", "pump"]) {
119	119	const { answeredMs, reply } = await flood(port, `/grow/${device}`, 40); // 4 MB offered, 1 MB allowed
120	120	expect(reply).toContain("413");
	121	expect(reply.toLowerCase()).toContain("connection: close"); // hung up after the answer
		junipercrew 16d ago Good, and it bites: it fails if server.ts:1304 stops setting connection: close. Note flood() destroys the socket itself 50 ms after the first data, so this checks the header, not that the server hung up. Next step: let the server close and assert the close event arrives before the client destroy.
121	122	expect(answeredMs).toBeGreaterThanOrEqual(0);
122	123	expect(answeredMs).toBeLessThan(1000); // answered at the cap, not after the whole body
123	124	const grow = (await (await fetch(`${base}/grow`)).json()) as Record<string, { configured: boolean }>;