Once you are done working on your project you can **deactivate** the virtual environment.

<div class="termy">

```console
$ deactivate
```

</div>

This way, when you run `python` it won't try to run it from that virtual environment with the packages installed there.

## Ready to Work { #ready-to-work }

Now you're ready to start working on your project.



/// tip

                buf.append(value).append("\n");
            }
            return buf.toString();
        }

    }

    /**
     * Sets the working directory for command execution.
     * @param workingDirectory The working directory.
     */
    public void setWorkingDirectory(final File workingDirectory) {
        this.workingDirectory = workingDirectory;
    }

    /**

    This command will be run from the **current working directory**, the same `/code` directory you set above with `WORKDIR /code`.

/// tip

Review what each line does by clicking each number bubble in the code. 👆

///

/// warning

Make sure to **always** use the **exec form** of the `CMD` instruction, as explained below.

///

                    Thread.sleep(delay);
                }

                // Attempt to reset the connection
                connection.reset();

                // Verify connection is working
                if (connection.getState() == RdmaConnection.RdmaConnectionState.ESTABLISHED) {
                    log.info("RDMA connection recovery successful after {} attempts", retryCount);
                    return true;

        byte[] buffer2 = createBasicNegotiateResponseBuffer();
        // Set maximum 16-bit value
        SMBUtil.writeInt2(65535, buffer2, 58);

        // Test should detect buffer overflow (this is working correctly!)
        SMBProtocolDecodingException exception = assertThrows(SMBProtocolDecodingException.class, () -> {
            response.readBytesWireFormat(buffer, 0);
        });

        SmbCircuitBreaker cbToClose = new SmbCircuitBreaker("close-test", 5, 2, 1000, 3, true, true, 100);

        // Verify it's working
        String result = cbToClose.executeWithCircuitBreaker(() -> "working");
        assertEquals("working", result);

        // Close it
        cbToClose.close();

        // Should not throw exception (close should be idempotent)
        cbToClose.close();

      // "C:foo" ("C:" - working dir of drive C on Windows)
      return parent;
    }

    // Paths that don't have a parent:
    if (path.getNameCount() == 0) {
      // "/", "C:\", "\" (no parent)
      // "" (undefined, though typically parent of working dir)
      // "C:" (parent of working dir of drive C on Windows)
      //
      // For working dir paths ("" and "C:"), return null because:

At the very least in the short term the resource needs to know how to look up the component that is required to perform the work. This needs to be made simple, for the time being we can write and test plugins working in the same realm until we get complete isolation working.

h3. Plugins need a specific metadata model

working on getting your pull request submitted to our internal repository. After
the change has been submitted internally, your pull request will be merged
automatically on GitHub.

If you want to contribute, start working through the TensorFlow codebase,
navigate to the
[GitHub "issues" tab](https://github.com/tensorflow/tensorflow/issues) and start

            task.getReportFile().convention(layout.getBuildDirectory().file("reports/dead-internal-links.txt"));
            task.getDocumentationRoot().convention(extension.getUserManual().getStagedDocumentation()); // working/usermanual/raw/
            task.getJavadocRoot().convention(layout.getBuildDirectory().dir("javadoc"));
            task.getReleaseNotesFile().convention(layout.getProjectDirectory().file("src/docs/release/notes.md"));