* limitations under the License.
 */

package com.google.common.testing.anotherpackage;

/** Does not check null, but should not matter since it's in a different package. */
@SuppressWarnings("unused") // For use by NullPointerTester
public class SomeClassThatDoesNotUseNullable {

  void packagePrivateButDoesNotCheckNull(String s) {}

        assertTrue(toStringResult.contains(message));
    }

    @Test
    public void test_multipleInstances() {
        // Test creating multiple instances with different messages
        LdapConfigurationException exception1 = new LdapConfigurationException("Error 1");
        LdapConfigurationException exception2 = new LdapConfigurationException("Error 2");

由於測試函式現在是非同步的，你也可以在測試中呼叫（並 `await`）其他 `async` 函式，和在程式碼其他地方一樣。

/// tip

如果在將非同步呼叫整合進測試時遇到 `RuntimeError: Task attached to a different loop`（例如使用 [MongoDB 的 MotorClient](https://stackoverflow.com/questions/41584243/runtimeerror-task-attached-to-a-different-loop) 時），請記得：需要事件迴圈的物件只應在非同步函式內實例化，例如在 `@app.on_event("startup")` 回呼中。

All the dependencies we have seen are a fixed function or class.

But there could be cases where you want to be able to set parameters on the dependency, without having to declare many different functions or classes.

Let's imagine that we want to have a dependency that checks if the query parameter `q` contains some fixed content.

But we want to be able to parameterize that fixed content.

import static org.elasticsearch.gradle.internal.conventions.GUtils.capitalize;

import static org.gradle.api.internal.artifacts.ArtifactAttributes.ARTIFACT_FORMAT;

/**
 * Provides a DSL and common configurations to define different types of
 * Elasticsearch distribution archives. See ':distribution:archives'.
 * <p>
 * This configures the default artifacts for the distribution specific
 * subprojects. We have subprojects for two reasons:

        // When
        int bytesRead = request.readBytesWireFormat(buffer, offset);

        // Then
        assertEquals(0, bytesRead);
    }

    @DisplayName("Should handle different completion filter combinations")
    @ParameterizedTest
    @CsvSource({ "1, FILE_NOTIFY_CHANGE_FILE_NAME", "2, FILE_NOTIFY_CHANGE_DIR_NAME", "4, FILE_NOTIFY_CHANGE_ATTRIBUTES",

# How To - Recipes { #how-to-recipes }

Here you will see different recipes or "how to" guides for **several topics**.

Most of these ideas would be more or less **independent**, and in most cases you should only need to study them if they apply directly to **your project**.

If something seems interesting and useful to your project, go ahead and check it, but otherwise, you might probably just skip them.

/// tip

### The Problem { #the-problem }

So, what's the problem with installing packages in the global Python environment?

At some point, you will probably end up writing many different programs that depend on **different packages**. And some of these projects you work on will depend on **different versions** of the same package. 😱

 * system is initialized.
 *
 * <p>This package includes:</p>
 * <ul>
 *   <li>Basic logging interfaces and implementations</li>
 *   <li>Support for different logging levels (DEBUG, INFO, WARN, ERROR)</li>
 *   <li>Accumulating loggers for deferred output</li>
 * </ul>
 *
 * @since 4.0.0
 */

## Origen { #origin }

Un origen es la combinación de protocolo (`http`, `https`), dominio (`myapp.com`, `localhost`, `localhost.tiangolo.com`) y puerto (`80`, `443`, `8080`).