net: write() on new net.Socket() before connect() is silently dropped (Node: ERR_SOCKET_CLOSED + destroy) #11156

Writing to a new net.Socket() before calling connect() behaves differently from Node. Node fails the write with ERR_SOCKET_CLOSED, destroys the socket and returns false. Perry accepts the bytes, counts them, and silently drops them: no error, no delivery. A program that relies on that 'error' never sees it, and the socket connects normally afterwards with the data gone.

import net from "node:net";
const srv = net.createServer((s) => {
  let got = 0;
  s.on("data", (d) => { got += d.length; });
  s.on("end", () => { console.log("server got", got); s.end(); srv.close(); });
});
srv.listen(0, "127.0.0.1", () => {
  const s = new net.Socket();
  s.on("error", (e: any) => console.log("error", e.code));
  s.on("close", () => { console.log("close"); srv.close(); });
  console.log("write", s.write("hi"));
  s.connect((srv.address() as any).port, "127.0.0.1", () => s.end());
});

Node 26.5.1:

write false
error ERR_SOCKET_CLOSED
close

Perry main (784ed8e) + #11130: write false (the return value is fixed in #11130), then no 'error'. The socket connects and the server receives 0 bytes.

Where: SocketState::command in crates/perry-ext-net/src/lib.rs. While awaiting_connect, a write is "accepted and counted, then dropped" by design, a carry-over from the old per-socket channel. Node's Socket._writeGeneric instead calls this.destroy(new ERR_SOCKET_CLOSED()) when there is no handle and the socket is not connecting.

Found while checking a CodeRabbit comment on #11130. That PR only fixes the write() return value (false) and does not arm 'drain' for these bytes.