IllegalArgumentException ex = assertThrows(IllegalArgumentException.class, () -> RequestParam.valueOf(badName));
        assertTrue(ex.getMessage().contains(badName), "Exception message should mention the bad name");
    }

    // Edge/Invalid: empty string is invalid for valueOf
    @ParameterizedTest
    @EmptySource
    @DisplayName("valueOf(\"\") throws IllegalArgumentException for empty input")

repository and [submit a pull request](https://help.github.com/articles/using-pull-requests). In the pull request, choose a title which sums up the changes that you have made, and in the body provide more details about what your changes do. Also mention the number of the issue where discussion has taken place, eg "Closes #123".

Then sit back and wait. There will probably be discussion about the pull request and, if any changes are needed, we would love to work with you to get your pull request...

But you can still document it as described in [Additional Responses in OpenAPI](additional-responses.md).

| *Required* | *Yes*    |

### AUTHPARAMS

Indicates STS API Authorization information. If you are familiar with AWS Signature V4 Authorization header, this STS API supports signature V4 authorization as mentioned [here](https://docs.aws.amazon.com/general/latest/gr/signature-version-4.html)

### DurationSeconds

 *
 * <p>Repositories can be configured at various levels:</p><ol>
 * <li>POM: Repositories can be specified in the {@code pom.xml} file under the {@code <repositories>} and {@code <pluginRepositories>} sections.</li>
 * <li>Settings: the {@code settings.xml} can be used to provide additional repositories in the three level of settings (user, project, installation).</li>
 * </ol>

 *
 * <p>Repositories can be configured at various levels:<ol>
 * <li>POM: Repositories can be specified in the {@code pom.xml} file under the {@code <repositories>} and {@code <pluginRepositories>} sections.</li>
 * <li>Settings: the {@code settings.xml} can be used to provide additional repositories in the three level of settings (user, project, installation).</li>
 * </ol>

                Strings.getOEMBytes(TEST_STRING, mockConfig);
            });

            assertTrue(exception.getMessage().contains("Unsupported OEM encoding"), "Exception should mention unsupported encoding");
            assertTrue(exception.getCause() instanceof UnsupportedEncodingException, "Cause should be UnsupportedEncodingException");
        }
    }

    @Nested

    }
    return dummy;
  }

  /**
   * Similar to the above, but keeps a boolean flag rather than checking for the string accumulated
   * so far being empty. As a result, it does not have the above-mentioned bug.
   */
  @Benchmark
  int booleanIfFirst(int reps) {
    int dummy = 0;
    for (int i = 0; i < reps; i++) {
      StringBuilder sb = new StringBuilder();
      boolean append = false;

 |                 ${maven.installation.conf}/toolchains.xml.
 |
 |                 NOTE: This location can be overridden with the CLI option:
 |
 |                 -it /path/to/installation/toolchains.xml
 |
 | The sections in this sample file are intended to give you a running start at
 | getting the most out of your Maven installation.
 |-->

                })
                .count();
        fixed |= fixedCombineSelfCount > 0;

        return fixed;
    }

    /**
     * Fixes duplicate dependencies in dependencies and dependencyManagement sections.
     */
    private boolean fixDuplicateDependencies(Document pomDocument, UpgradeContext context) {
        Element root = pomDocument.root();

        // Collect all dependency containers to process