String svgPatternCorrect = "image/svg\\+xml"; // Correct: \\+ matches literal +

        // Verify wrong pattern does NOT match (demonstrates the bug)
        assertFalse(svgMimetype.matches(svgPatternWrong));

        // Verify correct pattern DOES match (demonstrates the fix)
        assertTrue(svgMimetype.matches(svgPatternCorrect));

    /** The specified user already exists */
    int NT_STATUS_USER_EXISTS = 0xC0000063;
    /** The specified user does not exist */
    int NT_STATUS_NO_SUCH_USER = 0xC0000064;
    /** The specified network password is not correct */
    int NT_STATUS_WRONG_PASSWORD = 0xC000006a;
    /** Logon failure: unknown user name or bad password */
    int NT_STATUS_LOGON_FAILURE = 0xC000006d;
    /** Logon failure: user account restriction */

    // we create a test suite containing a test for every FuturesTest test method and we
    // set it as the name of the test.  Then in runTest we can reflectively load and invoke the
    // corresponding method on FuturesTest in the correct classloader.
    TestSuite suite = new TestSuite(AggregateFutureStateFallbackAtomicHelperTest.class.getName());
    for (Method method : FuturesTest.class.getDeclaredMethods()) {
      if (Modifier.isPublic(method.getModifiers())

                "Should throw exception for ACE count > 4096");
    }

    @Test
    @DisplayName("Test getType returns correct value")
    void testGetType() throws SMBProtocolDecodingException {
        // Prepare buffer with specific type value
        testBuffer[0] = 0x01; // revision
        testBuffer[1] = 0x00; // padding

If you added the return type annotation, tools and editors would complain with a (correct) error telling you that your function is returning a type (e.g. a dict) that is different from what you declared (e.g. a Pydantic model).

  <groupId>com.example.group</groupId>
  <artifactId>valid-version-sha1</artifactId>
  <version>${sha1}</version>

  <description>
    This will test if the validation for the ci friendly versions
    is working correct.
  </description>

import jcifs.internal.util.SMBUtil;

/**
 * Test class for FsctlPipeWaitRequest
 */
class FsctlPipeWaitRequestTest {

    @Test
    @DisplayName("Test constructor with name only sets correct fields")
    void testConstructorWithNameOnly() {
        // Test with simple pipe name
        String pipeName = "TestPipe";
        FsctlPipeWaitRequest request = new FsctlPipeWaitRequest(pipeName);

                You can run `GITHUB_TOKEN=<YourGitHubToken> ./gradlew docs:updateContributorsInReleaseNotes --milestone <milestone>` to update the release notes with correct contributors automatically.
                """.trimIndent()
            )
        }
    }

  <artifactId>valid-version-sha1plus</artifactId>
  <version>${sha1}${wrong}${revision}</version>

  <description>
    This will test if the validation for the ci friendly versions
    is working correct.
  </description>

  </parent>
  <groupId>com.example.group</groupId>
  <artifactId>valid-version-wrong</artifactId>
  <version>1.0</version>

  <description>
    This will test if the validation for the parent version
    is working correct in case of usage of LATEST
  </description>