select {
		case <-ctx.Done():
			return
		case <-r.qTimer.C:
			r.qCache.update()
		}
	}
}

// Delete deletes in-memory replication statistics for a bucket.
func (r *ReplicationStats) Delete(bucket string) {
	if r == nil {
		return
	}

	r.Lock()
	defer r.Unlock()
	delete(r.Cache, bucket)
}

// UpdateReplicaStat updates in-memory replica statistics with new values.

        assertNotNull(deleteResponse);
        assertFalse(deleteResponse.hasError());

        suggester.refresh();

        // Document-only should be deleted, Query-only should remain, Both should remain but as Query only
        assertEquals(2, suggester.getAllWordsNum());
        assertEquals(0, suggester.getDocumentWordsNum());
        assertEquals(2, suggester.getQueryWordsNum());

Normalmente você usa:

* `POST`: para criar dados.
* `GET`: para ler dados.
* `PUT`: para atualizar dados.
* `DELETE`: para deletar dados.

Portanto, no OpenAPI, cada um dos métodos HTTP é chamado de "operação".

Vamos chamá-los de "**operações**" também.

#### Defina um decorador de operação de rota { #define-a-path-operation-decorator }

                assertTrue(accessResult.getUrl().startsWith(url2));
                assertEquals(Constants.GET_METHOD, accessResult.getMethod());
            });

            dataService.delete(sessionId1);
            dataService.delete(sessionId2);
        } finally {
            try {
                server1.stop();
            } finally {
                server2.stop();
            }
        }
    }

            dataService.iterate(sessionId2, accessResult -> assertTrue(accessResult.getUrl().startsWith(url2)));

            dataService.delete(sessionId1);
            dataService.delete(sessionId2);
        } finally {
            try {
                server1.stop();
            } finally {
                server2.stop();
            }
        }
    }

    }

    /**
     * Delete a bad word.
     * @param badWord Bad word
     */
    public void delete(final String badWord) {
        if (logger.isDebugEnabled()) {
            logger.debug("Deleting bad word: index={}, word={}", arraySettings.arraySettingsIndexName, badWord);
        }
        arraySettings.delete(BAD_WORD_SETTINGS_KEY, badWord);
    }

    /**

	<target name="install.jars">
		<mkdir dir="${target.dir}" />
		<delete dir="${webinf.dir}/lib" />
		<mkdir dir="${webinf.dir}/lib" />
		<delete dir="${crawler.dir}/lib" />
		<mkdir dir="${crawler.dir}/lib" />
		<delete dir="${suggest.dir}/lib" />
		<mkdir dir="${suggest.dir}/lib" />
		<delete dir="${thumbnail.dir}/lib" />
		<mkdir dir="${thumbnail.dir}/lib" />
		<!-- annotation-api -->

        Artifact a = createArtifact("a", "0.0.1-SNAPSHOT");
        File file = new File(localRepository.getBasedir(), localRepository.pathOf(a));
        file.delete();
        a.setFile(file);

        File touchFile = updateCheckManager.getTouchfile(a);
        touchFile.delete();

        assertTrue(updateCheckManager.isUpdateRequired(a, remoteRepository));

        file.getParentFile().mkdirs();
        file.createNewFile();

import okhttp3.internal.platform.Platform

@TargetClass(BouncyCastlePlatform::class)
@Delete
class TargetBouncyCastlePlatform

@TargetClass(ConscryptPlatform::class)
@Delete
class TargetConscryptPlatform

@TargetClass(Jdk8WithJettyBootPlatform::class)
@Delete
class TargetJdk8WithJettyBootPlatform

@TargetClass(OpenJSSEPlatform::class)
@Delete
class TargetOpenJSSEPlatform

@TargetClass(Platform.Companion::class)

- Fixes an issue that can result in namespaced custom resources being orphaned when their namespace is deleted, if the CRD defining the custom resource is removed concurrently with namespaces being deleted, then recreated. ([#93790](https://github.com/kubernetes/kubernetes/pull/93790), [@liggitt](https://github.com/liggitt)) [SIG API Machinery and Apps]