*   Iterator<Entry<C, V>> i = row.entrySet().iterator(); // Must be in synchronized block
   *   while (i.hasNext()) {
   *     foo(i.next());
   *   }
   * }
   * }
   *
   * <p>Failure to follow this advice may result in non-deterministic behavior.
   *
   * <p>The returned table will be serializable if the specified table is serializable.
   *

 *  New: We've added `requestFailed()` and `responseFailed()` methods to `EventListener`. These
    are called instead of `requestBodyEnd()` and `responseBodyEnd()` in some failure situations.
    They may also be fired in cases where no event was published previously. In this release we did
    an internal rewrite of our event code to fix problems where events were lost or unbalanced.

            // Then
            verify(transportPool).logon(context, address, DEFAULT_PORT);
        }

        @Test
        @DisplayName("Should handle authentication failure during logon")
        void testLogonAuthenticationFailure() throws CIFSException {
            // Given
            doThrow(new CIFSException("Authentication failed")).when(transportPool).logon(context, address);

All Recipient's rights under this Agreement shall terminate if it fails to
comply with any of the material terms or conditions of this Agreement and
does not cure such failure in a reasonable period of time after becoming aware
of such noncompliance. If all Recipient's rights under this Agreement terminate,
Recipient agrees to cease use and distribution of the Program as soon as reasonably

# Application Exception
# ---------------------
# /- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
# five framework-embedded messages (don't change key names)
# - - - - - - - - - -/
errors.login.failure = 로그인에 실패했습니다.
errors.app.illegal.transition = 잘못된 전환입니다. 다시 시도하십시오.
errors.app.db.already.deleted = 다른 프로세스에 의해 삭제되었을 수 있습니다. 다시 시도하십시오.
errors.app.db.already.updated = 다른 프로세스에 의해 업데이트되었을 수 있습니다. 다시 시도하십시오.

- Fixed a bug where init containers may fail to start due to a temporary container runtime failure. ([#127214](https://github.com/kubernetes/kubernetes/pull/127214), [@SergeyKanzhelev](https://github.com/SergeyKanzhelev)) [SIG Node]

			},
			Bucket:    roi.Bucket,
			OpType:    replication.HealReplicationType,
			EventType: ReplicateHealDelete,
		}
		// heal delete marker replication failure or versioned delete replication failure
		if roi.ReplicationStatus == replication.Pending ||
			roi.ReplicationStatus == replication.Failed ||

* [fluentd-gcp addon] Fluentd now runs in its own network, not in the host one. ([#54395](https://github.com/kubernetes/kubernetes/pull/54395), [@crassirostris](https://github.com/crassirostris))

        // Cache clearing may not always occur in test environment
        // The real behavior depends on the actual SuggestJob implementation
    }

    // Test execute method with failure
    public void test_execute_failure() {
        createRequiredDirectories();

        // Setup failed process execution
        mockProcessHelper.setExitValue(1);

* Added anti-affinity to kube-dns pods. Otherwise the "no single point of failure" setting doesn't actually work (a single node failure can still take down the entire cluster). ([#57683](https://github.com/kubernetes/kubernetes/pull/57683), [@vainu-arto](https://github.com/vainu-arto))

### API-Machinery