private val useCompression: Boolean = true,
      private val out: Buffer,
    ) {
      /**
       * In the scenario where the dynamic table size changes multiple times between transmission of
       * header blocks, we need to keep track of the smallest value in that interval.
       */
      private var smallestHeaderTableSizeSetting = Integer.MAX_VALUE

        }

        public void addChannel(ChannelInfo channel) {
            channels.add(channel);
            if (primaryChannel == null) {
                primaryChannel = channel;
            }
        }

        public void removeChannel(ChannelInfo channel) {
            channels.remove(channel);
            if (primaryChannel == channel && !channels.isEmpty()) {
                primaryChannel = channels.get(0);

            reload(updater);
        }
    }

    /**
     * Reloads the character mapping items from the dictionary file.
     *
     * @param updater the mapping updater to use for writing changes, or null for read-only reload
     */
    protected void reload(final MappingUpdater updater) {
        try (CurlResponse curlResponse = dictionaryManager.getContentResponse(this)) {

// preferReaders can mark readers as preferred.
// These will be chosen before others.
func (p *parallelReader) preferReaders(prefer []bool) {
	if len(prefer) != len(p.orgReaders) {
		return
	}
	// Copy so we don't change our input.
	tmp := make([]io.ReaderAt, len(p.orgReaders))
	copy(tmp, p.orgReaders)
	p.readers = tmp
	// next is the next non-preferred index.
	next := 0
	for i, ok := range prefer {
		if !ok || p.readers[i] == nil {

 *
 * When merging `releaseX` branch into `master`, we should only use the release note from the `master` branch,
 * but sometimes changes on release notes.md was brought to master and merged unnoticed,
 * e.g https://github.com/gradle/gradle/pull/25825
 *
 * This script is to check if there is any merge commit that brings changes from release branch to master.
 * Usage: groovy CheckBadMerge.groovy <commit1> <commit2> ...

     * This class handles the process of writing changes to a temporary file
     * and then replacing the original file upon successful commit.
     */
    protected class SynonymUpdater implements Closeable {

        /** A flag indicating whether the changes have been committed. */
        protected boolean isCommit = false;

        /** The temporary file to write changes to. */
        protected File newFile;

        /** Witness resource change notification type */
        public static final int WITNESS_RESOURCE_CHANGE = 1;
        /** Witness client move notification type */
        public static final int WITNESS_CLIENT_MOVE = 2;
        /** Witness share move notification type */
        public static final int WITNESS_SHARE_MOVE = 3;
        /** Witness IP address change notification type */

Any metadata changes on the source object version, such as metadata updates via PutObjectTagging, PutObjectRetention, PutObjectLegalHold and COPY api are replicated in a similar manner to target version, with the `X-Amz-Replication-Status` again cycling through the same states.

objects encrypted on the server side, will be replicated if destination also supports encryption.

Replication status can be seen in the metadata on the source and destination objects. On the source side, the `X-Amz-Replication-Status` changes from `PENDING` to `COMPLETED` or `FAILED` after replication attempt either succeeded or failed respectively. On the destination side, a `X-Amz-Replication-Status` status of `REPLICA` indicates that the object was replicated successfully. Any replication...

        byte[] buffer = new byte[34];
        long create = 1600000000000L;
        long lastAccess = 1600000100000L;
        long lastWrite = 1600000200000L;
        long change = 1600000300000L;
        int attributes = 0x1234;
        // Convert Unix time to Windows FILETIME (100-nanosecond intervals since 1601)
        long MILLISECONDS_BETWEEN_1970_AND_1601 = 11644473600000L;