• judeng's avatar
    avoid incorrect shrinking of querybuf when client is reading a big argv (#12000) · e7f18432
    judeng authored
    this pr fix two wrongs:
    1. When client’s querybuf is pre-allocated for a fat argv, we need to update the
      querybuf_peak of the client immediately to completely avoid the unexpected
      shrinking of querybuf in the next clientCron (before data arrives to set the peak).
    2. the protocol's bulklen does not include `\r\n`, but the allocation and the data we
      read does. so in `clientsCronResizeQueryBuffer`, the `resize` or `querybuf_peak`
      should add these 2 bytes.
    
    the first bug is likely to hit us on large payloads over slow connections, in which case
    transferring the payload can take longer and a cron event will be triggered (specifically
    if there are not a lot of clients)
    e7f18432
networking.c 175 KB