}

    @ParameterizedTest(name = "Invalid usage causes NPE: {0}")
    @MethodSource("npePublicGetters")
    void getters_withoutTree_throwNPE(String name, org.junit.jupiter.api.function.Executable call) {
        // Each call is invalid without a held tree and should throw NPE
        assertThrows(NullPointerException.class, call);
    }

    static java.util.stream.Stream<Arguments> wrapExceptions() {

- [Configuring etcd](https://github.com/minio/minio/blob/master/docs/sts/etcd.md)

### Setup MinIO with Identity Provider

Make sure we have followed the previous step and configured each software independently, once done we can now proceed to use MinIO STS API and MinIO server to use these credentials to perform object API operations.

#### KeyCloak

```
export MINIO_ROOT_USER=minio

> Please note that losing the `MINIO_KMS_SECRET_KEY` will cause data loss
> since you will not be able to decrypt the IAM/configuration data anymore.
For distributed MinIO deployments, specify the *same* `MINIO_KMS_SECRET_KEY` for each MinIO server process.

At any point in time you can switch from `MINIO_KMS_SECRET_KEY` to a full KMS
deployment. You just need to import the generated key into KES - for example via

Replication from a source bucket to multiple destination buckets is supported. For each of the targets, repeat the steps to configure a remote target ARN and add replication rules to the source bucket's replication config.

              public ImmutableList<AclEntry> value() {
                return acl;
              }
            };
        return () -> attribute;
      } catch (IOException e) {
        // We throw a new exception each time so that the stack trace is right.
        return () -> {
          throw new IOException("Could not find user", e);
        };
      }
    }

    private static String getUsername() {
      /*

            byte[] buffer2 = createValidWriteResponse(200, 100);

            response1.readBytesWireFormat(buffer1, 0);
            response2.readBytesWireFormat(buffer2, 0);

            // Each instance should maintain its own state
            assertEquals(100, response1.getCount());
            assertEquals(50, response1.getRemaining());
            assertEquals(200, response2.getCount());

        Arrays.fill(fileId2, (byte) 0xFF);

        byte[] fileId3 = new byte[16];
        for (int i = 0; i < 16; i++) {
            fileId3[i] = (byte) i;
        }

        // When & Then for each file ID
        testFileIdWriting(fileId1);
        testFileIdWriting(fileId2);
        testFileIdWriting(fileId3);
    }

    private void testFileIdWriting(byte[] fileId) {

        assertNotNull(resumeKey2);
        assertEquals((byte) 0x22, resumeKey2[0]);

        // Verify it's a different array
        assertNotSame(resumeKey1, resumeKey2, "Should create new array on each decode");
    }

   * #descendingMultiset()} will not reflect any changes you make to the behavior of methods such as
   * {@link #add(Object)} or {@link #pollFirstEntry}. This skeleton implementation correctly
   * delegates each of its operations to the appropriate methods of this {@code
   * ForwardingSortedMultiset}.
   *
   * <p>In many cases, you may wish to override {@link #descendingMultiset()} to return an instance

  echo 'sure they are present on your system and try again.'
  exit 1
fi

# "TFCI_MACOS_BAZEL_TEST_DIR_PATH" specifies the directory that Bazel should use
# when running tests. Each test will be executed in a separate subdirectory
# inside this directory. TF Mac builds need ~150 GB of disk space to be able to
# run all the tests. Since TFCI Mac VMs execute Bazel test commands in a