* are inherently approximate, routinely affected by periodic clock corrections. Because this class
 * (by default) uses {@link System#nanoTime}, it is unaffected by these changes.
 *
 * <p>Use this class instead of direct calls to {@link System#nanoTime} for two reasons:
 *
 * <ul>
 *   <li>The raw {@code long} values returned by {@code nanoTime} are meaningless and unsafe to use

        // Assert
        assertArrayEquals(r2, r1);
        assertEquals(24, r1.length);
    }

    @Test
    @DisplayName("getNTLM2Response: returns 24 bytes and changes with inputs")
    void testGetNTLM2Response_basic() throws GeneralSecurityException {
        // Arrange
        byte[] pwdHash = NtlmUtil.getNTHash("password");
        byte[] server = hex("0102030405060708");

For the things that need changes in your Pydantic models, the Pydantic team built [`bump-pydantic`](https://github.com/pydantic/bump-pydantic).

A command line tool that will **process your code** and update most of the things **automatically** for you. Make sure you have your code in git first, and review each of the changes to make sure everything is correct before committing the changes.

### Pydantic v1

   * calling {@code get(columnKey, rowKey)} on the generated table always returns the same value as
   * calling {@code get(rowKey, columnKey)} on the original table. Updating the original table
   * changes the contents of the transposed table and vice versa.
   *
   * <p>The returned table supports update operations as long as the input table supports the

    ContainsBothWithMultisetFirst reMultisetFirst = reserialize(multisetFirst);
    assertThat(reMultisetFirst.a.isEmpty()).isFalse();
    // The following NPE is a side effect of our changes to avoid mutating `final` fields.
    assertThrows(NullPointerException.class, () -> reMultisetFirst.z.multiset.isEmpty());

    ContainsBothWithContainsMultisetFirst reContainsMultisetFirst =

	// should skip healing the disk
	SkipHealing bool

	// Active lifecycle, if any on the bucket
	lifeCycle *lifecycle.Lifecycle `msg:"-"`

	// optional updates channel.
	// If set updates will be sent regularly to this channel.
	// Will not be closed when returned.
	updates     chan<- dataUsageEntry `msg:"-"`
	replication replicationConfig     `msg:"-"`
}

import org.codelibs.core.exception.IORuntimeException;

/**
 * The {@code DynamicProperties} class extends {@link Properties} to provide dynamic
 * loading and storing of properties from a file. It monitors the file for changes
 * and reloads the properties if the file is updated. This class is thread-safe and
 * ensures that the properties are always up-to-date.
 *
 * <p>Key Features:
 * <ul>

        if (getMojos() == null) {
            return null; // no mojo in this POM
        }

        // TODO could we use a map? Maybe if the parent did that for components too, as this is too vulnerable to
        // changes above not being propagated to the map
        for (MojoDescriptor desc : getMojos()) {
            if (goal.equals(desc.getGoal())) {
                return desc;
            }
        }
        return null;

import org.opensearch.action.admin.indices.alias.get.GetAliasesResponse;
import org.opensearch.action.admin.indices.create.CreateIndexResponse;
import org.opensearch.transport.client.Client;

/**
 * Test class for refactoring changes made to Suggester class.
 *
 * Tests cover:
 * - Index alias helper method (getIndicesForAlias)
 * - Edge cases for switchIndex with EXPECTED_INDEX_COUNT
 * - Index lifecycle with refactored methods
 */

Sometimes a backward compatibility change spans two versions. A common case is a new functionality
that needs a BWC bridge in an unreleased versioned of a release branch (for example, 5.x).
To test the changes, you can instruct Gradle to build the BWC version from a another remote/branch combination instead of
pulling the release branch from GitHub. You do so using the `bwc.remote` and `bwc.refspec.BRANCH` system properties: