// Single node on list
          if (next == null) {
            newTable.set(headIndex, head);
          } else {
            // Reuse the consecutive sequence of nodes with the same target
            // index from the end of the list. tail points to the first
            // entry in the reusable list.
            E tail = head;
            int tailIndex = headIndex;

    /**
     * Deletes a document from the specified index with optimistic concurrency control.
     *
     * @param index       the index name
     * @param id          the document ID
     * @param seqNo       the sequence number for optimistic concurrency control
     * @param primaryTerm the primary term for optimistic concurrency control
     * @return true if the document was deleted successfully, false otherwise

    // Check that a fresh connection was created, either immediately or after attempting reuse.
    // We know that a fresh connection was created if the server recorded a request with sequence
    // number 0. Since the client may have attempted to reuse the broken connection just before
    // creating a fresh connection, the server may have recorded 2 requests at this point. The order

- Ensure Job status updates are batched by 1s. This fixes an unlikely scenario when a sequence of immediately 
  completing pods could trigger a sequence of non-batched Job status updates. ([#118470](https://github.com/kubernetes/kubernetes/pull/118470), [@mimowo](https://github.com/mimowo)) [SIG Apps]

- Increased the maximum backoff delay of the endpointslice controller to match the expected sequence of delays when syncing Services. ([#112353](https://github.com/kubernetes/kubernetes/pull/112353), [@dgrisonnet](https://github.com/dgrisonnet))

     */
    String getIndexFieldVersion();

    /**
     * Get the value for the key 'index.field.seq_no'. <br>
     * The value is, e.g. _seq_no <br>
     * comment: Field name for sequence number in the index.
     * @return The value of found property. (NotNull: if not found, exception but basically no way)
     */
    String getIndexFieldSeqNo();

    /**

- StreamWatcher now calls HandleCrash at appropriate sequence. ([#93108](https://github.com/kubernetes/kubernetes/pull/93108), [@lixiaobing1](https://github.com/lixiaobing1))

The sequence of execution before FastAPI 0.106.0 was like this diagram:

Time flows from top to bottom. And each column is one of the parts interacting or executing code.

```mermaid
sequenceDiagram