// samba 4 starting with some version does not seem to handle this correctly :(
        try ( SmbWatchHandle w = this.base
                .watch(FileNotifyInformation.FILE_NOTIFY_CHANGE_ATTRIBUTES | FileNotifyInformation.FILE_NOTIFY_CHANGE_LAST_WRITE, false) ) {
            try ( SmbFile cr = new SmbFile(this.base, "modified") ) {
                cr.createNewFile();
                setupWatch(w);

  lacks_tests:
    if:
      - {{ ('lacks_tests' | isEnabledAutomation(pr)) }}
      - {{ includes_src_changes }}
      - {{ not (includes_test_changes) }}
      - {{ not (is_docs_only_change) }}
      - {{ not (is_formatting_only_change) }}
    run:
      - action: add-label@v1
        args:
          label: "⚠️ Lacks Tests"
          color: {{ colors.yellow }}
      - action: add-comment@v1
        args:

                "Cannot change the artifactId for an attached artifact." + " It is derived from the main artifact.");
    }

    public List<ArtifactVersion> getAvailableVersions() {
        return parent.getAvailableVersions();
    }

    public void setAvailableVersions(List<ArtifactVersion> availableVersions) {
        throw new UnsupportedOperationException("Cannot change the version information for an attached artifact."

            seenApiChanges.add(change)
            return Violation.accept(member, "${rejection.getHumanExplanation()}. Reason for accepting this: <b>Upgraded property</b>")
        }

        def acceptanceJson = new AcceptedApiChange(
            change.type,
            change.member,
            '[ADD YOUR CUSTOM REASON HERE]',
            change.changes
        )

}

# Note: this is excluded on the full code base, since any submitted code must
# have passed Google's internal style guidelines.
@test "Check formatting for C++ files" {
    skip "clang-format doesn't match internal clang-format checker"
    echo "clang-format is recommended. Here are the suggested changes:"
    echo "============================="
    grep -e '\.h$' -e '\.cc$' $BATS_FILE_TMPDIR/changed_files > $BATS_TEST_TMPDIR/files || true

## FAQ

> Why is this change needed?

Before, there were two separate mechanisms - S3 objects got encrypted using a KMS,
if present, and the IAM / configuration data got encrypted with the root credentials.
Now, MinIO encrypts IAM / configuration and S3 objects with a KMS, if present. This
change unified the key-management aspect within MinIO.

                    errors << "From non-nullable to nullable breaking change"
                } else if (oldNullability && !newNullability) {
                    warnings << "Nullability changed from nullable to non-nullable"
                }
            } else if (oldNullability != newNullability) {
                errors << "Nullability breaking change"
            }

        } else if (member instanceof JApiConstructor) {

        params {
            text(
                "gitUserEmail",
                "",
                label = "Git user.email Configuration",
                description = "Enter the git 'user.email' configuration to commit change under",
                display = ParameterDisplay.PROMPT,
                allowEmpty = true
            )
            text(
                "confirmationCode",
                "",

    "groups" : [ {
      "testProject" : "largeJavaMultiProject",
      "coverage" : {
        "per_commit" : [ "linux", "windows", "macOs" ]
      }
    } ]
  }, {
    "testId" : "org.gradle.performance.regression.java.JavaIncrementalExecutionPerformanceTest.assemble for non-abi change",
    "groups" : [ {

     */
    @Override
    public byte[] getAnsiHash ( CIFSContext tc, byte[] chlng ) throws GeneralSecurityException {
        if ( this.hashesExternal ) {
            return this.ansiHash;
        }
        return super.getAnsiHash(tc, chlng);
    }


    /**
     * {@inheritDoc}
     *