* necessarily indicate application-layer success: `response` may still indicate an unhappy HTTP
   * response code like 404 or 500.
   *
   * @throws IOException if the request could not be executed due to cancellation, a connectivity
   *     problem or timeout. Because networks can fail during an exchange, it is possible that the
   *     remote server accepted the request before the failure.

            }
        } catch (final MaxLengthExceededException e) {
            throw e;
        } catch (final Exception e) {
            if (buf.length() == 0) {
                throw new ExtractException("Could not extract a content.", e);
            }
        } finally {
            CloseableUtil.closeQuietly(ais);
        }

        return buf.toString().trim();
    }

    /**

 * such custom interfaces directly; they are implemented only in subclasses. Therefore, forwarding
 * {@code equals} would break symmetry, as the forwarding object might consider itself equal to the
 * object being tested, but the reverse could not be true. This behavior is consistent with the
 * JDK's collection wrappers, such as {@link java.util.Collections#unmodifiableCollection}. Use an

It might also help avoid confusion for new developers that see an unused parameter in your code and could think it's unnecessary.

///

/// info

In this example we use invented custom headers `X-Key` and `X-Token`.

But in real cases, when implementing security, you would get more benefits from using the integrated [Security utilities (the next chapter)](../security/index.md){.internal-link target=_blank}.

    tests themselves and not the code being tested that needs that access, though there's no
    obvious way to ensure that.

    We could consider arranging things so that only the tests we know need this would get
    the add-opens. Right now that doesn't seem worth the effort, though.
    -->
    <test.add.opens>
      --add-opens java.base/java.lang=ALL-UNNAMED

      /*
       * Using weak references here could let us release exceptions earlier, but:
       *
       * 1. On Android, querying a WeakReference blocks if the GC is doing an otherwise-concurrent
       * pass.
       *
       * 2. We would probably choose to compare exceptions using == instead of equals() (for

        // and set its own specific fields (ptype, flags).
        // The fact that the object is successfully created implies the super constructor was called.
    }

    // Additional tests could be added here if MsrpcSamrOpenAlias had more methods or complex logic.
    // For this specific class, the constructor is the main point of logic.

	DIR="initial-data"
	FILE="file1"
	DATA_DRIVE=$(find_erasure_set_for_file $FILE $DIR)
	STATUS=$?
	if [ $STATUS -ne 0 ]; then
		echo -e "${RED}Could not find erasure set for file: ${FILE}${NC}"
		echo -e "${RED}"${FUNCNAME[0]}" Failed${NC}"
		TESTS_RUN_STATUS=$((TESTS_RUN_STATUS & 0))
		return 1
	fi

	# Remove single xl.meta -- status still green

     * execute Queue#drainTo is not added *on top* of waiting for the timeout (which could make
     * the timeout arbitrarily inaccurate, given a queue that is slow to drain).
     */
    long deadline = System.nanoTime() + unit.toNanos(timeout);
    int added = 0;
    while (added < numElements) {
      // we could rely solely on #poll, but #drainTo might be more efficient when there are multiple

            BeanUtil.copyMapToBean(dataMap, obj);
            return obj;
        } catch (final Exception e) {
            throw new CrawlerSystemException("Could not create/copy a data map to " + dataClass, e);
        }
    }

    /*
     * (non-Javadoc)
     *