- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 333 for seventy (0.04 sec)
-
android/guava-tests/test/com/google/common/collect/ImmutableMapTest.java
.put(2, "deux") .put(70, "soixante-dix") .put(70, "septante") .put(70, "seventy") .put(1, "one") .put(2, "two"); ImmutableMap<Integer, String> map = builder.buildKeepingLast(); assertMapEquals(map, 1, "one", 2, "two", 70, "seventy"); } public void testBuildKeepingLast_smallTableSameHash() { String key1 = "QED"; String key2 = "R&D";
Registered: Fri Sep 05 12:43:10 UTC 2025 - Last Modified: Thu Aug 07 16:05:33 UTC 2025 - 36.7K bytes - Viewed (0) -
src/test/java/org/codelibs/fess/entity/SearchLogEventTest.java
// Create different implementations SearchLogEvent event1 = new TestSearchLogEvent("id1", 1L, "type1"); SearchLogEvent event2 = new NullSearchLogEvent(); SearchLogEvent event3 = new EmptySearchLogEvent(); // Test polymorphic behavior SearchLogEvent[] events = { event1, event2, event3 }; for (SearchLogEvent event : events) { // All methods should be callable without exceptions
Registered: Thu Sep 04 12:52:25 UTC 2025 - Last Modified: Tue Aug 19 14:09:36 UTC 2025 - 11.6K bytes - Viewed (0) -
docs/en/docs/advanced/events.md
In this case, the `startup` event handler function will initialize the items "database" (just a `dict`) with some values. You can add more than one event handler function. And your application won't start receiving requests until all the `startup` event handlers have completed. ### `shutdown` event { #shutdown-event } To add a function that should be run when the application is shutting down, declare it with the event `"shutdown"`:
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Sun Aug 31 09:15:41 UTC 2025 - 7.9K bytes - Viewed (0) -
docs/pt/docs/advanced/events.md
E sua aplicação não irá começar a receber requisições até que todos os manipuladores de eventos de `startup` sejam concluídos. ### Evento `shutdown` Para adicionar uma função que deve ser executada quando a aplicação estiver encerrando, declare ela com o evento `"shutdown"`: {* ../../docs_src/events/tutorial002.py hl[6] *}
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Mon Nov 18 02:25:44 UTC 2024 - 8.5K bytes - Viewed (0) -
docs/es/docs/advanced/events.md
Estas funciones pueden ser declaradas con `async def` o `def` normal. ### Evento `startup` Para añadir una función que debería ejecutarse antes de que la aplicación inicie, declárala con el evento `"startup"`: {* ../../docs_src/events/tutorial001.py hl[8] *} En este caso, la función manejadora del evento `startup` inicializará los ítems de la "base de datos" (solo un `dict`) con algunos valores.
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Mon Dec 30 18:26:57 UTC 2024 - 8.2K bytes - Viewed (0) -
docs/de/docs/advanced/events.md
Diese Funktionen können mit `async def` oder normalem `def` deklariert werden. ### `startup`-Event Um eine Funktion hinzuzufügen, die vor dem Start der Anwendung ausgeführt werden soll, deklarieren Sie diese mit dem Event `startup`: {* ../../docs_src/events/tutorial001.py hl[8] *}
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Mon Nov 18 02:25:44 UTC 2024 - 9K bytes - Viewed (0) -
cmd/event-notification.go
"github.com/minio/minio/internal/event" xhttp "github.com/minio/minio/internal/http" "github.com/minio/minio/internal/pubsub" "github.com/minio/pkg/v3/policy" ) // EventNotifier - notifies external systems about events in MinIO. type EventNotifier struct { sync.RWMutex targetList *event.TargetList bucketRulesMap map[string]event.RulesMap }
Registered: Sun Sep 07 19:28:11 UTC 2025 - Last Modified: Fri Jun 21 22:22:24 UTC 2024 - 7.7K bytes - Viewed (0) -
src/test/java/org/codelibs/fess/util/ErrorToWarnRewritePolicyTest.java
.build(); LogEvent event3 = Log4jLogEvent.newBuilder() .setLoggerName("third.logger") .setLevel(Level.ERROR) .setMessage(new SimpleMessage("test message 3")) .build(); LogEvent result1 = policy.rewrite(event1); LogEvent result2 = policy.rewrite(event2); LogEvent result3 = policy.rewrite(event3);
Registered: Thu Sep 04 12:52:25 UTC 2025 - Last Modified: Thu Aug 07 03:06:29 UTC 2025 - 11.9K bytes - Viewed (0) -
docs/de/docs/advanced/testing-events.md
# Events testen: Hochfahren – Herunterfahren Wenn Sie in Ihren Tests Ihre Event-Handler (`startup` und `shutdown`) ausführen wollen, können Sie den `TestClient` mit einer `with`-Anweisung verwenden:
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Mon Nov 18 02:25:44 UTC 2024 - 268 bytes - Viewed (0) -
docs/en/docs/advanced/testing-events.md
# Testing Events: lifespan and startup - shutdown { #testing-events-lifespan-and-startup-shutdown } When you need `lifespan` to run in your tests, you can use the `TestClient` with a `with` statement: {* ../../docs_src/app_testing/tutorial004.py hl[9:15,18,27:28,30:32,41:43] *} You can read more details about the ["Running lifespan in tests in the official Starlette documentation site."](https://www.starlette.io/lifespan/#running-lifespan-in-tests)
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Sun Aug 31 10:29:21 UTC 2025 - 615 bytes - Viewed (0)