Kubernetes was previously detecting that the image filesystem was split, even when that was not really the case ([#128344](https://github.com/kubernetes/kubernetes/pull/128344), [@kannon92](https://github.com/kannon92)) [SIG Node]
- Fixed an issue in the kubelet that showed when writeable layers and read-only layers were at different paths within the same mount.

.375rem) calc(.75em + .375rem) no-repeat}.custom-select.is-valid:focus,.was-validated .custom-select:valid:focus{border-color:#28a745;box-shadow:0 0 0 .2rem rgba(40,167,69,.25)}.form-check-input.is-valid~.form-check-label,.was-validated .form-check-input:valid~.form-check-label{color:#28a745}.form-check-input.is-valid~.valid-feedback,.form-check-input.is-valid~.valid-tooltip,.was-validated .form-check-input:valid~.valid-feedback,.was-validated .form-check-input:valid~.valid-tooltip{display:block}.cus...

     *
     * @param dictFile the dictionary file metadata to store
     * @param file the actual file containing the dictionary content
     * @throws DictionaryException if the file was updated by another process,
     *         if the file doesn't exist, or if there's an error during storage
     */
    public void store(final DictionaryFile<? extends DictionaryItem> dictFile, final File file) {

        // Act: first valid next should be the second element
        assertTrue(itr.hasNext());
        SmbResource r = itr.next();

        // Assert: the invalid name was skipped, valid one returned
        assertNotNull(r);
        assertTrue(r.getName().startsWith("OKSERVER"), "Expected valid entry to be adapted");
        assertFalse(itr.hasNext());
    }

    @Test

    /**
     * Constructs a new ContentNotFoundException with the specified parent URL and URL.
     *
     * @param parentUrl the URL of the parent document
     * @param url the URL of the content that was not found
     */
    public ContentNotFoundException(final String parentUrl, final String url) {
        super("Not Found: " + url + " Parent: " + parentUrl, false, false);
    }

    private static final long serialVersionUID = 1L;

    /**
     * Constructs a new FessUserNotFoundException with the specified username.
     *
     * @param username the username that was not found
     */
    public FessUserNotFoundException(final String username) {
        super("User is not found: " + username);
    }

              errorMessage.set("Set call exited before future was complete.");
            }
          });
      executor.execute(
          () -> {
            future.setException(new IllegalArgumentException("failure"));
            if (!future.isDone()) {
              errorMessage.set("SetException call exited before future was complete.");
            }
          });
      executor.execute(

    public void test_constructorWithString_longMessage() {
        // Test with a long message
        String message = "This is a very long error message that describes in detail why the job was not found. "
                + "The job with identifier XYZ123 was expected to be in the system but could not be located "
                + "after searching through all available job registries and scheduled task databases.";

        return registrationId;
    }

    /**
     * Simulate a witness unregistration
     *
     * @param registrationId the registration ID to remove
     * @return true if registration was found and removed
     */
    public boolean unregisterWitness(String registrationId) {
        MockRegistration removed = registrations.remove(registrationId);
        if (removed != null) {

- Previously, when trying to allocate devices through DRA for a node timed out, scheduling would proceed with another node if any had the necessary resources. This potentially hid that a node was ignored. Worse, if scheduling was slow overall, the pod was incorrectly moved to "unschedulable" and only retried after a periodic sweep. Now timeouts are errors that are always visible as pod scheduling failures and get retried with per-pod exponential backoff. ([#137607](http...