... another small complaint about the currentPushRequests & locking is that we obtain a lock here, and then again on 775. In theory (but only in theory) other code could sneak in and double-add the stream Id to currentPushRequests because the contains/add pair is not guarded by a single lock.