if meta, err := xl.AppendTo(metaDataPoolGet()); err == nil {
					if best.reusable {
						metaDataPoolPut(best.metadata)
					}
					best.metadata = meta
					best.cached = xl
				}
			}
			toMerge = toMerge[:0]
		}
		if best.name > last {
			select {
			case <-ctxDone:
				return ctx.Err()
			case out <- *best:
				last = best.name
			}
		} else if serverDebugLog {

        String preference = config.getRdmaProvider();
        return createProvider(preference != null ? preference : "auto");
    }

    /**
     * Select the best available RDMA provider
     *
     * @return best RDMA provider, or null if none available
     */
    public static RdmaProvider selectBestProvider() {
        // Try providers in order of preference

The Gradle codebase has evolved over time and has a mixture of simple getter/setter methods, Provider API and things in between.  It can be hard to follow best practices because Gradle provided types are reused in unexpected ways and extended by third party plugins.

Given these constraints, we cannot always follow best practices.  This ADR proposes the way we should handle the use of Provider APIs in the gradle/gradle codebase.

## Decision

			bucket: o.Bucket,
			status: scanStateNone,
		}
	}

	// Create new and add.
	best := o.newMetacache()
	b.caches[o.ID] = best
	b.cachesRoot[best.root] = append(b.cachesRoot[best.root], best.id)
	b.updated = true
	b.debugf("returning new cache %s, bucket: %v", best.id, best.bucket)
	return best
}

// cleanup removes redundant and outdated entries.
func (b *bucketMetacache) cleanup() {

   */
  public static HashFunction concatenating(
      HashFunction first, HashFunction second, HashFunction... rest) {
    // We can't use Lists.asList() here because there's no hash->collect dependency
    List<HashFunction> list = new ArrayList<>();
    list.add(first);
    list.add(second);
    Collections.addAll(list, rest);
    return new ConcatenatedHashFunction(list.toArray(new HashFunction[0]));
  }

  /**

</blockquote>

## Investigation { #investigation }

# ADR-0001 - Use Architectural Decision Records

## Date

2023-12-01

## Context

In a distributed team with many subteams, the best solution to communicate decisions is to use a format accessible by everyone in charge of development.

We use *Specification* and *Discovery* documents stored in Google Drive, but they present some downsides:

  #   title: Learn to build high-quality web apps with best practices
  #   img: https://fastapi.tiangolo.com/img/sponsors/testdriven.svg
  - url: https://lambdatest.com/?utm_source=fastapi&utm_medium=partner&utm_campaign=sponsor&utm_term=opensource&utm_content=webpage
    title: LambdaTest, AI-Powered Cloud-based Test Orchestration Platform
    img: https://fastapi.tiangolo.com/img/sponsors/lambdatest.png

  stars: 1176
  owner_login: langchain-ai
  owner_html_url: https://github.com/langchain-ai
- name: restish
  html_url: https://github.com/rest-sh/restish
  stars: 1140
  owner_login: rest-sh
  owner_html_url: https://github.com/rest-sh
- name: odmantic
  html_url: https://github.com/art049/odmantic
  stars: 1138
  owner_login: art049
  owner_html_url: https://github.com/art049
- name: authx

    has good test coverage, so look at some existing tests if you're unsure how
    to go about it.
2.  All contributions must be licensed Apache 2.0 and all files must have a copy
    of the boilerplate license comment (can be copied from an existing file).
3.  Files should be formatted according to Google's [Java style guide][].
4.  Do your best to have a [well-formed commit message][] for the change.