Question client doc handleOp not debounce ?

Fetch only sends a new fetch command if no fetches are inflight in source code, but in the real environment is not. fetch is not natural debouncing, when receive multiple op action from other client, it will send multiple fetch command to server, and receive multiple op segments (same ops) from server.

source: https://github.com/share/sharedb/blob/master/lib/client/doc.js#L329

Doc.prototype._handleOp = function(err, message) {
  ...

  if (this.version == null || message.v > this.version) {
    // This will happen in normal operation if we become subscribed to a
    // new document via a query. It can also happen if we get an op for
    // a future version beyond the version we are expecting next. This
    // could happen if the server doesn't publish an op for whatever reason
    // or because of a race condition. In any case, we can send a fetch
    // command to catch back up.
    //
    // Fetch only sends a new fetch command if no fetches are inflight, which
    // will act as a natural debouncing so we don't send multiple fetch
    // requests for many ops received at once.
    this.fetch();
    return;
  }
  ...

receive multiple same op segments

Start in lib/client/doc.js at Doc.prototype._handleOp and read the surrounding fetch handling. Reproduce the reported case of multiple op actions from another client, then compare the observed fetch requests and returned op segments with the comment's claim about debouncing.