servers:
  - url: http://localhost:8080/api/v1
tags:
  - name: search
    description: Search operations
  - name: popularword
    description: Popular word operations
  - name: monitor
    description: Monitoring operations
  - name: suggest
    description: Suggest operations
  - name: favorite
    description: Favorite operations
paths:
  /documents:
    get:
      tags:
        - search

    }

    /**
     * Add a pending operation
     *
     * @param operation operation to add
     */
    public void addPendingOperation(CommonServerMessageBlock operation) {
        pendingOperations.add(operation);
    }

    /**
     * Remove a pending operation
     *
     * @param operation operation to remove
     * @return true if operation was removed
     */

And we can add a list of `dependencies` that will be added to all the *path operations* in the router and will be executed/solved for each request made to them.

/// tip

        @Test
        @DisplayName("delete operation should work correctly")
        void testDelete() throws CIFSException {
            // When/Then
            assertDoesNotThrow(() -> mockResource.delete(), "Delete operation should not throw exception");
            verify(mockResource).delete();
        }

        @Test
        @DisplayName("copy operation should work correctly")

    }

    /**
     * Get total number of RDMA read operations
     *
     * @return read operation count
     */
    public long getRdmaReads() {
        return rdmaReads.get();
    }

    /**
     * Get total number of RDMA write operations
     *
     * @return write operation count
     */
    public long getRdmaWrites() {
        return rdmaWrites.get();
    }

```

...that's because the client generator uses the OpenAPI internal **operation ID** for each *path operation*.

OpenAPI requires that each operation ID is unique across all the *path operations*, so FastAPI uses the **function name**, the **path**, and the **HTTP method/operation** to generate that operation ID, because that way it can make sure that the operation IDs are unique.

But I'll show you how to improve that next. 🤓

max_sleep      (duration)  maximum sleep duration between objects to slow down heal operation. eg. 2s
max_io         (int)       maximum IO requests allowed between objects to slow down heal operation. eg. 3
drive_workers  (int)       the number of workers per drive to heal a new disk replacement.
```

Y podemos agregar una lista de `dependencies` que se añadirá a todas las *path operations* en el router y se ejecutarán/solucionarán por cada request que les haga.

/// tip | Consejo

        }

        assertTrue(latch.await(10, TimeUnit.SECONDS), "Concurrent operations should complete");
        executor.shutdown();

        // Circuit breaker should have handled concurrent operations
        assertTrue(successCount.get() > 0, "Should have some successful operations");
        assertTrue(failureCount.get() > 0, "Should have some failed operations");
    }

    @Test

```

...eso es porque el generador del cliente usa el **operation ID** interno de OpenAPI para cada *path operation*.

OpenAPI requiere que cada operation ID sea único a través de todas las *path operations*, por lo que FastAPI usa el **nombre de la función**, el **path**, y el **método/operación HTTP** para generar ese operation ID, porque de esa manera puede asegurarse de que los operation IDs sean únicos.