> For a comprehensive overview, please visit the [official Gradle project homepage](https://gradle.org).

---

### 🚀 **Getting Started**

Starting with Gradle is easy with these essential resources. Follow these to install Gradle, set up initial projects, and explore supported platforms:

- **Network & I/O** (`org.codelibs.core.net`, `org.codelibs.core.nio`) - URL utilities, UUID generation, MIME type detection, and NIO channel operations

## 🚀 Getting Started

### Requirements
- **Java 21 or higher** (Required for modern language features)
- **Maven 3.6+** or **Gradle 7+** for build management
- **Optional**: SLF4J or Commons Logging for logging support

            assertArrayEquals(expectedKey, handle.getSessionKey());
        }

        @Test
        @DisplayName("Should propagate CIFSException when getting session key")
        void testGetSessionKey_ThrowsCIFSException() throws Exception {
            DcerpcPipeHandle handle = createMockedDcerpcPipeHandle();
            CIFSException exception = new CIFSException("Test exception");

                throw new MojoExecutionException(e);
            }
        }

        @Override
        public void setLog(Log log) {}

        @Override
        public Log getLog() {
            return null;
        }
    }

                // Implementation for raw payload
            }

            @Override
            public byte[] getRawPayload() {
                // Implementation for getting raw payload
                return null;
            }

            @Override
            public boolean isRetainPayload() {
                // Implementation for retain payload flag

    <!--
      | We may potentially want to export these, but right now I'm not sure that anything Guice specific needs
      | to be made available to plugin authors. If we find people are getting fancy and want to take advantage of
      | Guice specifics we can expose that later. Really some testing needs to be done to see full hiding

    response = client.post(
        "/admin/?token=jessica", headers={"X-Token": "fake-super-secret-token"}
    )
    assert response.status_code == 200, response.text
    assert response.json() == {"message": "Admin getting schwifty"}


def test_admin_invalid_header(client: TestClient):
    response = client.post("/admin/", headers={"X-Token": "invalid"})
    assert response.status_code == 400, response.text

 |                 NOTE: This location can be overridden with the CLI option:
 |
 |                 -is /path/to/installation/settings.xml
 |
 | The sections in this sample file are intended to give you a running start at
 | getting the most out of your Maven installation. Where appropriate, the default
 | values (values used when the setting is not specified) are provided.
 |
 |-->
<settings xmlns="http://maven.apache.org/SETTINGS/2.0.0"

                <description></description>
            </project>
            """;

        Document doc = Document.of(pomXml);
        Element root = doc.root();

        // Test getting text from existing elements
        assertEquals("4.0.0", root.childText("modelVersion"), "Should get modelVersion text");
        assertEquals("test", root.childText("groupId"), "Should get groupId text");

The exception handler will receive a `Request` and the exception.

{* ../../docs_src/handling_errors/tutorial004_py39.py hl[2,14:19] *}

Now, if you go to `/items/foo`, instead of getting the default JSON error with:

```JSON
{
    "detail": [
        {
            "loc": [
                "path",
                "item_id"
            ],