class Puma::MiniSSL::Socket

go ahead and actually block in write_nonblock.
So for the time being (and since write blocking is quite rare),

it had already written the data in.
code would pass the same data in, but the engine would think
write_nonblock call might raise an exception and later
an engine because after we write+extract, the socket
is that it means we'd have to have the ability to rewind
The problem with implementing it properly

def write_nonblock(data, *_)
  write data
end