See the [security policy](https://golang.org/security) for details.

The recommended way to file an issue is by running `go bug`.
Otherwise, when filing an issue, make sure to answer these five questions:

1. What version of Go are you using (`go version`)?
2. What operating system and processor architecture are you using?
3. What did you do?
4. What did you expect to see?

If you open a GitHub Issue, here is our policy:

1.  It must be a bug/performance issue or a feature request or a build issue or
    a documentation issue (for small doc fixes please send a PR instead).
1.  Make sure the Issue Template is filled out.
1.  The issue should be related to the repo it is created in.

**Here's why we have this policy:** We want to focus on the work that benefits
the whole community, e.g., fixing bugs and adding features. Individual support

 * Custom qualifier annotations should be annotated with {@code @Qualifier}.
 * <p>
 * Example of creating a custom qualifier:
 * <pre>
 * {@literal @}Qualifier
 * {@literal @}Retention(RUNTIME)
 * public @interface Database {
 *     String value();
 * }
 * </pre>
 *
 * @see Named
 * @since 4.0.0
 */
@Target(ANNOTATION_TYPE)
@Retention(RUNTIME)
@Documented

        assertTrue(testConfig.disallowCompound.contains("Smb2TreeConnectRequest"));
    }

    @Test
    @DisplayName("Test initDefaults with pre-set machine ID")
    void testInitDefaultsWithPresetMachineId() throws Exception {
        BaseConfiguration testConfig = new BaseConfiguration(false);
        byte[] customMachineId = new byte[32];

Docker provides standardized mechanisms to run docker containers as non-root users.

#### GNU/Linux and macOS (regular user)

On Linux and macOS you can use `--user` to run the container as regular user.

> NOTE: make sure --user has write permission to *${HOME}/data* prior to using `--user`.

```sh
mkdir -p ${HOME}/data
docker run \
  -p 9000:9000 \
  -p 9001:9001 \
  --user $(id -u):$(id -g) \
  --name minio1 \

 * </ul>
 *
 * <p>Example usage:</p>
 * <pre>
 * Toolchain toolchain = ...; // Obtain a Toolchain instance
 * String type = toolchain.getType(); // Get the type of the toolchain
 * String version = toolchain.getVersion(); // Get the version of the toolchain
 * </pre>
 *
 *
 * @since 4.0.0
 * @see JavaToolchain
 * @see org.apache.maven.api.services.ToolchainManager
 */

 * to create an exception instance with a message, a cause, or both.
 *
 * <p>Usage examples:</p>
 * <pre>
 * throw new SuggesterException("An error occurred");
 * throw new SuggesterException(new IOException("IO error"));
 * throw new SuggesterException("An error occurred", new IOException("IO error"));
 * </pre>
 *
 * @see RuntimeException
 */
public class SuggesterException extends RuntimeException {

			// If we are unable to parse them and the prefix field looks like
			// an ASCII string, then we fallback on the pre-Go1.8 behavior
			// of treating these fields as the USTAR prefix field.
			//
			// Note that this will not use the fallback logic for all possible
			// files generated by a pre-Go1.8 toolchain. If the generated file
			// happened to have a prefix field that parses as valid

## Steps to Reproduce (for bugs)
<!--- Provide a link to a live example, or an unambiguous set of steps to -->
<!--- reproduce this bug. Include code to reproduce, if relevant -->
<!--- and make sure you have followed https://github.com/minio/minio/tree/release/docs/debugging to capture relevant logs -->

1.
2.
3.
4.

## Context
<!--- How has this issue affected you? What are you trying to accomplish? -->

 * <p>
 * Example usage:
 * <pre>
 * public class CustomProjectScopeProvider implements ProjectScopeProvider {
 *     public Collection&lt;ProjectScope&gt; provides() {
 *         return Collections.singleton(projectScope("integration-test"));
 *     }
 * }
 * </pre>
 *
 * @see org.apache.maven.api.ProjectScope
 * @see org.apache.maven.api.spi.ExtensibleEnumProvider