assertEquals(0, stats.getTotalBlocked());
        assertEquals(0, stats.getAccountsLocked());
        assertEquals(0, stats.getIpsBlocked());

        // Create some activity
        String username = "statsuser";
        String ip = "192.168.1.10";

        // Lock out an account
        for (int i = 0; i < 3; i++) {
            rateLimiter.checkAttempt(username, ip);
            rateLimiter.recordFailure(username, ip);

    @DisplayName("available() on SMB1 returns 0 and marks closed on disconnected statuses")
    void available_smb1_disconnectedStatuses(int status) throws Exception {
        // Verify SMB1 path: disconnected/server-closed statuses yield 0 and mark fd closed
        SmbPipeInputStream stream = newStreamWithInit(false);

        when(handle.ensureOpen()).thenReturn(fd);

	ResetStatusesMap           map[string]string                 // map of ARN-> stringified reset id and timestamp for all the targets
}

// Equal returns true if replication state is identical for version purge statuses and (replica)tion statuses.
func (rs *ReplicationState) Equal(o ReplicationState) bool {
	return rs.ReplicaStatus == o.ReplicaStatus &&
		rs.ReplicationStatusInternal == o.ReplicationStatusInternal &&

	var basePrefix string
	switch userType {
	case svcUser:
		basePrefix = iamConfigServiceAccountsPrefix
	case stsUser:
		basePrefix = iamConfigSTSPrefix
	default:
		basePrefix = iamConfigUsersPrefix
	}

	ctx, cancel := context.WithCancel(ctx)
	defer cancel()

func (ies *IAMEtcdStore) loadUsers(ctx context.Context, userType IAMUserType, m map[string]UserIdentity) error {
	var basePrefix string
	switch userType {
	case svcUser:
		basePrefix = iamConfigServiceAccountsPrefix
	case stsUser:
		basePrefix = iamConfigSTSPrefix
	default:
		basePrefix = iamConfigUsersPrefix
	}

	cctx, cancel := context.WithTimeout(ctx, defaultContextTimeout)
	defer cancel()

`@ExperimentalOkHttpApi`. You can safely use this release in production.

 *  Fix: Attempt to read the response even if sending the request failed. This makes it possible
    to handle response statuses like `HTTP/1.1 431 "Request Header Fields Too Large`.

 *  Fix: Handle multiple 1xx responses.

 *  Fix: Address a performance bug in our internal task runner. We had a race condition that could