interface FlowControlListener {
  /**
   * Notification that the receiving stream flow control window has changed.
   * [WindowCounter] generally carries the client view of total and acked bytes.
   */
  fun receivingStreamWindowChanged(
    streamId: Int,
    windowCounter: WindowCounter,
    bufferSize: Long,
  )

  /**
   * Notification that the receiving connection flow control window has changed.

      if (outFinished) {
        this.sink.finished = true
        notifyAll() // Because doReadTimeout() may have changed.
      }
    }

    // Only DATA frames are subject to flow-control. Transmit the HEADER frame if the connection
    // flow-control window is fully depleted.
    if (!flushHeaders) {
      withLock {
        flushHeaders = (connection.writeBytesTotal >= connection.writeBytesMaximum)
      }
    }

        ],
        "parallelizationMethod": {
          "name": "TestDistribution"
        }
      },
      {
        "subprojects": [
          "base-services",
          "build-cache",
          "flow-services",
          "input-tracking",
          "internal-integ-testing",
          "model-core",
          "persistent-cache",
          "process-memory-services",
          "scala",
          "snapshots",

  static final Iterable<Integer> ALL_INTEGER_CANDIDATES;

  static {
    ImmutableSet.Builder<Integer> intValues = ImmutableSet.builder();
    // Add boundary values manually to avoid over/under flow (this covers 2^N for 0 and 31).
    intValues.add(Integer.MAX_VALUE - 1, Integer.MAX_VALUE);
    // Add values up to 40. This covers cases like "square of a prime" and such.
    for (int i = 1; i <= 40; i++) {

  /** Settings we communicate to the peer. */
  val okHttpSettings =
    Settings().apply {
      // Flow control was designed more for servers, or proxies than edge clients. If we are a client,
      // set the flow control window to 16MiB.  This avoids thrashing window updates every 64KiB, yet
      // small enough to avoid blowing up the heap.
      if (builder.client) {

    "name": "core-api",
    "path": "subprojects/core-api",
    "unitTests": true,
    "functionalTests": true,
    "crossVersionTests": false
  },
  {
    "name": "core-flow-services-api",
    "path": "platforms/core-configuration/core-flow-services-api",
    "unitTests": false,
    "functionalTests": true,
    "crossVersionTests": false
  },
  {
    "name": "core-kotlin-extensions",

     */
    RelevanceEvaluationResult evaluateResults(String userMessage, String query, List<Map<String, Object>> searchResults);

    /**
     * Generates an answer using document content (synchronous version for non-enhanced flow).
     *
     * @param userMessage the user's message
     * @param documents the documents with content
     * @param history the conversation history
     * @return the chat response
     */

        SuggestCreator.Options options = new SuggestCreator.Options();
        assertNotNull(options);
    }

    // Test create and purge full flow
    @Test
    public void test_createAndPurge_fullFlow() {
        // Test full flow of create and purge
        SuggestCreator.Options options = new SuggestCreator.Options();
        assertNotNull(options);
    }

    // Test system property setting

        assertTrue(testClient.lastCreateOnly);
    }

    // ==========================================================================
    // reindexConfigIndices - full rebuild flow
    // ==========================================================================

    @Test
    public void test_reindexConfigIndices_skipsDocIndex() {
        testClient.existsIndexResult = true;

 *  Fix: Don't lose HTTP/2 flow control bytes when incoming data races with a stream close. If this
    happened enough then eventually the connection would stall.

 *  Fix: Acknowledge and apply inbound HTTP/2 settings atomically. Previously we had a race where we
    could use new flow control capacity before acknowledging it, causing strict HTTP/2 servers to
    fail the call.