`HandshakeCertificates` holds the TLS certificates required for a TLS handshake. On the server
    it keeps your `HeldCertificate` and its chain. On the client it keeps the root certificates
    that are trusted to sign a server's certificate chain. `HandshakeCertificates` also works with
    mutual TLS where these roles are reversed.

}`,
		},
		{
			name:       "limit-2",
			query:      `select * from s3object[*].person[*] limit 1`,
			wantResult: `{"Id":1,"Name":"Anshu","Address":"Templestowe","Car":"Jeep"}`,
			withJSON:   `{ "person": [ { "Id": 1, "Name": "Anshu", "Address": "Templestowe", "Car": "Jeep" }, { "Id": 2, "Name": "Ben Mostafa", "Address": "Las Vegas", "Car": "Mustang" }, { "Id": 3, "Name": "Rohan Wood", "Address": "Wooddon", "Car": "VW" } ] }`,
		},
		{

     * <p>
     * If there are Maven3 passwords presents in settings, this results in doubled warnings emitted. So Plexus DI
     * creation call keeps "emitSettingsWarnings" false. If there are fatal issues, it will anyway "die" at that
     * spot before warnings would be emitted.
     * <p>

    /**
     * @return {@code true} if the current thread has acquired this lock.
     */
    boolean isAcquiredByCurrentThread();
  }

  /**
   * A {@code LockGraphNode} associated with each lock instance keeps track of the directed edges in
   * the lock acquisition graph.
   */
  private static final class LockGraphNode {

    /**

 * href="https://www.javadoc.io/doc/com.github.ben-manes.caffeine/caffeine/latest/com.github.benmanes.caffeine/com/github/benmanes/caffeine/cache/AsyncLoadingCache.html">their
 * deep support for asynchronous operations</a>. But if you want to migrate to Caffeine with minimal
 * code changes, you can use <a

bauhaus
bayern
bb
bbc
bbs.tr
bbt
bbva
bc.ca
bcg
bcn
bd.se
be
be.eu.org
beagleboard.io
bearalvahki.no
bearalváhki.no
beardu.no
beats
beauty
bedzin.pl
beep.pl
beer
beiarn.no
bel.tr
belau.pw
belem.br
belluno.it
benevento.it
bentley
bentre.vn
beppu.oita.jp
berg.no
bergamo.it
bergen.no
berlevag.no
berlevåg.no
berlin

				"application/atom+xml",
				"application/atomcat+xml",
				"application/atomicmail",
				"application/atomsvc+xml",
				"application/auth-policy+xml",
				"application/batch-smtp",
				"application/beep+xml",
				"application/bizagi-modeler",
				"application/cals-1840",
				"application/ccxml+xml",
				"application/cea-2018+xml",
				"application/cellml+xml",
				"application/cnrp+xml",

 * href="https://www.javadoc.io/doc/com.github.ben-manes.caffeine/caffeine/latest/com.github.benmanes.caffeine/com/github/benmanes/caffeine/cache/AsyncLoadingCache.html">their
 * deep support for asynchronous operations</a>. But if you want to migrate to Caffeine with minimal
 * code changes, you can use <a

Go <code>const</code> declarations defined in the current package.
Go assembly should avoid making assumptions about the layout of Go
types and instead use these constants.
This improves the readability of assembly code, and keeps it robust to
changes in data layout either in the Go type definitions or in the
layout rules used by the Go compiler.
</p>

<p>
Constants are of the form <code>const_<i>name</i></code>.

bauhaus
bayern
bb
bbc
bbs.tr
bbt
bbva
bc.ca
bcg
bcn
bd.se
be
be.eu.org
beagleboard.io
bearalvahki.no
bearalváhki.no
beardu.no
beats
beauty
bedzin.pl
beep.pl
beer
beiarn.no
bel.tr
belau.pw
belem.br
belluno.it
benevento.it
bentley
bentre.vn
beppu.oita.jp
berg.no
bergamo.it
bergen.no
berlevag.no
berlevåg.no
berlin