want to analyze the set of transitive dependencies, in particular during early lifecycle phases where
            full dependency resolution might fail due to projects which haven't been built yet.
          </description>
        </field>
        <field>
          <name>dependencyCollection</name>
          <version>2.0.0+</version>
          <type>String</type>

problems. If your service has multiple IP addresses, OkHttp will attempt alternate addresses if the
first connect fails. This is necessary for IPv4+IPv6 and services hosted in redundant data
centers. OkHttp supports modern TLS features (TLS 1.3, ALPN, certificate pinning). It can be
configured to fall back for broad connectivity.

Using OkHttp is easy. Its request/response API is designed with fluent builders and immutability. It

        legacySupport.setSession(session);
    }

    protected abstract String component();

    /**
     * Return an existing file, not a directory - causes creation to fail.
     *
     * @throws Exception
     */
    protected ArtifactRepository badLocalRepository() throws Exception {
        String path = "target/test-repositories/" + component() + "/bad-local-repository";

            },
            traditional: true
          })
            .done(function (obj) {
              suggestor.createAutoCompleteList(obj);
            })
            .fail(function (xhr, status, error) {
              if (console && console.error) {
                console.error("Suggestion request failed:", status, error);
              }
              suggestor.hideSuggestionBox();

   * implementation of this pattern is [gRPC][grpc].
   *
   * Because the encoding of interleaved data is not well-defined for HTTP/1, duplex request
   * bodies may only be used with HTTP/2. Calls to HTTP/1 servers will fail before the HTTP request
   * is transmitted. If you cannot ensure that your client and server both support HTTP/2, do not
   * use this feature.
   *
   * ### Duplex APIs
   *

            }
        });

        final ProtocolHelper protocolHelper = new ProtocolHelper();
        protocolHelper.init();

        try {
            protocolHelper.isValidWebProtocol(null);
            fail("Should throw exception for null URL");
        } catch (Exception e) {
            // Expected
            assertNotNull(e);
        }
    }

    @Test
    public void test_isValidFileProtocol_nullUrl() {

        QueryContext context = new QueryContext("test", false);
        TermQuery termQuery = new TermQuery(new Term("field", "value"));

        try {
            queryProcessor.execute(context, termQuery, 1.0f);
            fail();
        } catch (InvalidQueryException e) {
            // expected
            assertTrue(e.getMessage().contains("Unknown q:"));
        }
    }

    @Test

    try {
      entrySet.add((Entry<K, V>) entryToAdd);
      fail("Expected UnsupportedOperationException or NullPointerException.");
    } catch (UnsupportedOperationException | NullPointerException e) {
      // Expected.
    }
    assertInvariants(map);

    try {
      entrySet.addAll(singleton((Entry<K, V>) entryToAdd));
      fail("Expected UnsupportedOperationException or NullPointerException.");

        });

        // The StoredLtrQueryBuilder.params() method requires non-null params
        // so this should throw a NullPointerException
        try {
            ltrQueryRescorer.evaluate(null);
            fail("Expected NullPointerException");
        } catch (NullPointerException e) {
            // Expected behavior - StoredLtrQueryBuilder requires non-null params
            assertNotNull(e);
        }
    }

		var c ciphertext
		if err := c.UnmarshalJSON(b); err != nil {
			// It may happen that a random ciphertext starts with '{' and ends with '}'.
			// In such a case, parsing will fail but we must not return an error. Instead
			// we return the ciphertext as it is.
			return b, kms.AES256
		}

		b = b[:0]
		b = append(b, c.Bytes...)
		b = append(b, c.IV...)
		b = append(b, c.Nonce...)