// calculate names?

  /**
   * Creates an {@link Executor} that renames the {@link Thread threads} that its tasks run in.
   *
   * <p>The names are retrieved from the {@code nameSupplier} on the thread that is being renamed
   * right before each task is run. The renaming is best effort, if a {@link SecurityManager}

   networkResponse, priorResponse, protocol, receivedResponseAtMillis, request, sentRequestAtMillis
 * **Route**: address, proxy, socketAddress
 * **TlsVersion**: javaName

#### Renamed Functions

* **Headers.of()**: for symmetry with `listOf()`, `setOf()`, etc., we’ve replaced
  `Headers.of(String...)` with `headersOf(vararg String)`.

#### Extension Functions

    void testGetAction() throws SMBProtocolDecodingException {
        int expectedAction = FileNotifyInformation.FILE_ACTION_RENAMED_NEW_NAME;
        byte[] buffer = createValidNotificationBuffer("renamed.txt", expectedAction);

        notifyInfo.decode(buffer, 0, buffer.length);

        assertEquals(expectedAction, notifyInfo.getAction());
    }

    @Test

{* ../../docs_src/generate_clients/tutorial004_py39.py *}

//// tab | Node.js

```Javascript
{!> ../../docs_src/generate_clients/tutorial004.js!}
```

////

With that, the operation IDs would be renamed from things like `items-get_items` to just `get_items`, that way the client generator can generate simpler method names.

        void testRenameToSameFile() throws MalformedURLException, SmbException {
            // Arrange
            doThrow(new SmbException("Cannot rename to same file")).when(smbFile).renameTo(smbFile);

            // Act & Assert
            assertThrows(SmbException.class, () -> smbFile.renameTo(smbFile));
        }

        @Test
        void testCreateNewFileWhenExists() throws SmbException, IOException {
            // Arrange

        val testFramework = if (modularization == ModularizationOption.WITH_LIBRARY_PROJECTS) BuildInitTestFramework.JUNIT_JUPITER else descriptor.defaultTestFramework

        // clear the target directory to remove renamed files and reset the README file
        target.asFile.deleteRecursively()

Spark/Hadoop workloads which use Hadoop MR Committer v1/v2 algorithm upload objects to a temporary prefix in a bucket. These objects are 'renamed' to a different prefix on Job commit. Object storage admins are forced to configure separate ILM policies to expire these objects and their versions to reclaim space.

### Solution

         * File was removed from the directory
         */
        FILE_REMOVED,
        /**
         * File was modified in the directory
         */
        FILE_MODIFIED,
        /**
         * Directory was renamed
         */
        DIRECTORY_RENAMED,
        /**
         * File or directory attributes were changed
         */
        ATTRIBUTES_CHANGED
    }

    /**
     * SMB2 File Action constants
     */

Template.`var_scope` property renamed to `.variable_scope` *
SyncReplicasOptimizer is removed and SyncReplicasOptimizerV2 renamed to
SyncReplicasOptimizer. * `tf.zeros_initializer()` and `tf.ones_initializer()`
now return a callable that must be called with initializer arguments, in your
code replace `tf.zeros_initializer` with `tf.zeros_initializer()`. *
`SparseTensor.shape` has been renamed to `SparseTensor.dense_shape`. Same for

            assertTrue(result.success(), "Model upgrade should succeed");
            assertTrue(result.modifiedCount() > 0, "Should have converted modules to subprojects");

            // Verify modules element was renamed to subprojects - use the updated document from pomMap
            Document updatedDocument = pomMap.get(Paths.get("pom.xml"));
            Editor editor = new Editor(updatedDocument);
            Element root = editor.root();