* and the <code>jcifs.smb1.resolveOrder</code> property. Changing
 * jCIFS name resolution properties can greatly affect the behavior of
 * the client and may be necessary for proper operation.
 * <p>
 * This class should be used in favor of {@code InetAddress} to resolve
 * hostnames on LANs and WANs that support a mixture of NetBIOS/WINS and
 * DNS resolvable hosts.
 */

public class UniAddress {

        // Insert an element that's not in the ELEMENT_ORDER (should be appended at the end)
        DomUtils.insertContentElement(root, "customElement", "custom value");

        String xmlOutput = DomUtils.toXml(doc);

        int versionIndex = xmlOutput.indexOf("<version>");
        int customElementIndex = xmlOutput.indexOf("<customElement>");

        // Custom element should be appended at the end

@app.get("/item", response_model=Item)
async def read_item():
    return {
        "id": uuid.uuid4(),
        "name": "Island In The Moon",
        "price": 12.99,
        "description": "A place to be playin' and havin' fun",
        "tags": ["breater"],
    }


client = TestClient(app)


def test_annotations():
    response = client.get("/item")
    assert response.status_code == 200, response.text

    /**
     * Returns an {@link Iterable} that wraps the array for use in a for-each statement.
     *
     * @param <T> the type of elements
     * @param items the array of elements to iterate (must not be {@literal null})
     * @return an {@link Iterable} wrapping the array
     */
    public static <T> Iterable<T> iterable(final T... items) {
        assertArgumentNotNull("items", items);

 * beyond the standard ones provided by Maven (like jar, war, ear, etc.). Implementations of this
 * interface will be discovered through the Java ServiceLoader mechanism and their provided
 * packaging types will be available throughout the Maven build process.
 * <p>
 * Example usage:
 * <pre>
 * public class CustomPackagingProvider implements PackagingProvider {

        if (variableName == null) {
            String msg = "The value should not be null: variableName=null value=" + value;
            throw new IllegalArgumentException(msg);
        }
        if (value == null) {
            String msg = "The value should not be null: variableName=" + variableName;
            throw new IllegalArgumentException(msg);
        }
    }

In many cases, when you use regular Pydantic models without customizations, you will be able to automate most of the process of migrating from Pydantic v1 to Pydantic v2.

You can use [`bump-pydantic`](https://github.com/pydantic/bump-pydantic) from the same Pydantic team.

This tool will help you to automatically change most of the code that needs to be changed.

        TestFessSystemException exception = new TestFessSystemException(message, true, true);

        assertEquals(message, exception.getMessage());
        assertNull(exception.getCause());

        // Stack trace should be populated
        assertTrue(exception.getStackTrace().length > 0);
    }

    @Test
    public void test_constructor_withNonWritableStackTrace() {
        // Test protected constructor with non-writable stack trace

       *
       * TODO(cpovirk): It might be nice for our InterruptibleTask subclasses to null out their
       *  `callable` fields automatically. That would make it less important for us to null out the
       * reference to `task` here (though it's still nice to do so in case our reference to the
       * executor keeps it alive). Ideally, nulling out `callable` would be the responsibility of

// bytes from the infinite stream consisting of repeated
// concatenations of `alphabets`.
//
// The skipOffset (generally = 0) can be used to skip a given number
// of bytes from the beginning of the infinite stream. This is useful
// to compare such streams of bytes that may be split up, because:
//
// Given the function:
//
//	f := func(r io.Reader) string {
//	          b, _ := io.ReadAll(r)