TestHttpServletRequest request = new TestHttpServletRequest();

        request.setRequestURI("/api/v1/search");
        assertTrue(manager.matches(request));

        request.setRequestURI("/api/v2/label");
        assertTrue(manager.matches(request));

        request.setRequestURI("/api/search");
        assertFalse(manager.matches(request));

        request.setRequestURI("/other/v1/search");

  public static <E> SynchronousQueue<E> newSynchronousQueue() {
    return new SynchronousQueue<>();
  }

  /**
   * Drains the queue as {@link BlockingQueue#drainTo(Collection, int)}, but if the requested {@code
   * numElements} elements are not available, it will wait for them up to the specified timeout.
   *
   * @param q the blocking queue to be drained
   * @param buffer where to add the transferred elements

2. The client connects to the idle daemon and sends it a request to do some work. If the daemon is no longer running, the client starts again.
3. If the daemon is not able to run the request, for example it is already running a request or is shutting down, it rejects the request. The client starts again.
4. The daemon runs the request, sending back data such as logging output or tooling API events and intermediate models while doing so.

	for _, ep := range testServer.Disks {
		for _, disk := range ep.Endpoints {
			os.RemoveAll(disk.Path)
		}
	}
}

// Truncate request to simulate unexpected EOF for a request signed using streaming signature v4.
func truncateChunkByHalfSigv4(req *http.Request) (*http.Request, error) {
	bufReader := bufio.NewReader(req.Body)
	hexChunkSize, chunkSignature, err := readChunkLine(bufReader)
	if err != nil {
		return nil, err

                    appendJson("order", entity.getOrder(), buf).append(',');
                    appendJson("query-requested-at", entity.getQueryRequestedAt(), buf).append(',');
                    appendJson("requested-at", entity.getRequestedAt(), buf);
                    buf.append('}');
                    buf.append('\n');
                    try {

  readOnlyRootFilesystem: false

# Additational pod annotations
podAnnotations: {}

# Additional pod labels
podLabels: {}

## Configure resource requests and limits
## ref: http://kubernetes.io/docs/user-guide/compute-resources/
##
resources:
  requests:
    memory: 16Gi

## List of policies to be created after minio install
##

---
- job:
    name: "elastic+elasticsearch+pull-request+part-1-windows"
    display-name: "elastic / elasticsearch - pull request part-1 windows"
    description: "Testing of Elasticsearch pull requests - part-1 windows"
    node: "windows-immutable"
    workspace: "C:\\Users\\jenkins\\workspace\\pr-part-1\\${BUILD_NUMBER}"
    scm:
      - git:
          refspec: "+refs/pull/${ghprbPullId}/*:refs/remotes/origin/pr/${ghprbPullId}/*"
          branches:

    }

    /**
     * Get the number of send credits requested
     *
     * @return credits requested
     */
    public int getCreditsRequested() {
        return creditsRequested;
    }

    /**
     * Set the number of send credits requested
     *
     * @param creditsRequested credits to request
     */
    public void setCreditsRequested(int creditsRequested) {

# MinIO Pull Request Guidelines

These guidelines ensure high-quality commits in MinIO’s GitHub repositories, maintaining 
a clear, valuable commit history for our open-source projects. They apply to all contributors, 
fostering efficient reviews and robust code.

## Why Pull Requests?

Pull Requests (PRs) drive quality in MinIO’s codebase by:
- Enabling peer review without pair programming.
- Documenting changes for future reference.

#  limitations under the License.
#

# https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema

name: Feature request
description: File a proposal for new feature, improvement
labels: ["enhancement"]

body:
  - type: markdown
    attributes:
      value: |