- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 239 for starai (0.06 sec)
-
src/main/resources/fess_indices/fess/it/stopwords.txt
stiano starò starai starà staremo starete staranno starei staresti starebbe staremmo stareste starebbero stavo stavi stava stavamo stavate stavano stetti stesti stette stemmo steste stettero stessi stesse stessimo stessero
Registered: Sat Dec 20 09:19:18 UTC 2025 - Last Modified: Mon Nov 27 12:59:36 UTC 2023 - 1.8K bytes - Viewed (0) -
src/main/resources/fess_indices/_aws/fess.json
"facevate", "facevano", "feci", "facesti", "fece", "facemmo", "faceste", "fecero", "facessi", "facesse", "facessimo", "facessero", "facendo", "sto", "stai", "sta", "stiamo", "stanno", "stia", "stiate", "stiano", "starò", "starai", "starà", "staremo", "starete", "staranno", "starei", "staresti", "starebbe", "staremmo", "stareste", "starebbero", "stavo", "stavi", "stava", "stavamo", "stavate", "stavano", "stetti", "stesti", "stette", "stemmo", "steste", "stettero", "stessi", "stesse", "stessimo", "stessero",...
Registered: Sat Dec 20 09:19:18 UTC 2025 - Last Modified: Sat Jun 14 00:36:40 UTC 2025 - 117.3K bytes - Viewed (0) -
src/main/resources/fess_indices/_cloud/fess.json
"facevate", "facevano", "feci", "facesti", "fece", "facemmo", "faceste", "fecero", "facessi", "facesse", "facessimo", "facessero", "facendo", "sto", "stai", "sta", "stiamo", "stanno", "stia", "stiate", "stiano", "starò", "starai", "starà", "staremo", "starete", "staranno", "starei", "staresti", "starebbe", "staremmo", "stareste", "starebbero", "stavo", "stavi", "stava", "stavamo", "stavate", "stavano", "stetti", "stesti", "stette", "stemmo", "steste", "stettero", "stessi", "stesse", "stessimo", "stessero",...
Registered: Sat Dec 20 09:19:18 UTC 2025 - Last Modified: Sat Feb 27 09:26:16 UTC 2021 - 117.3K bytes - Viewed (0) -
src/main/resources/fess_indices/fess/es/stopwords.txt
vuestro vuestra vuestros vuestras esos esas estoy estás está estamos estáis están esté estés estemos estéis estén estaré estarás estará estaremos estaréis estarán estaría estarías estaríamos estaríais estarían estaba estabas estábamos estabais estaban estuve estuviste estuvo estuvimos estuvisteis
Registered: Sat Dec 20 09:19:18 UTC 2025 - Last Modified: Mon Nov 27 12:59:36 UTC 2023 - 2.2K bytes - Viewed (0) -
src/archive/tar/testdata/star.tar
Russ Cox <******@****.***> 1410149331 -0400
Registered: Tue Dec 30 11:13:12 UTC 2025 - Last Modified: Mon Sep 08 04:08:51 UTC 2014 - 3K bytes - Viewed (0) -
fess-crawler/src/test/java/org/codelibs/fess/crawler/interval/impl/HostIntervalControllerTest.java
final long start1 = System.nanoTime(); controller.delayBeforeProcessing(); final long elapsed1 = (System.nanoTime() - start1) / 1000000; assertTrue("First access should not delay", elapsed1 < 50); // Second access to same host - should delay q.setUrl("http://example.com/page2"); final long start2 = System.nanoTime();
Registered: Sat Dec 20 11:21:39 UTC 2025 - Last Modified: Mon Nov 24 03:59:47 UTC 2025 - 11.4K bytes - Viewed (0) -
build-logic/jvm/src/main/kotlin/gradlebuild.start-scripts.gradle.kts
} configurations { create("gradleScriptsElements") { isCanBeResolved = false isCanBeConsumed = true attributes.attribute(Usage.USAGE_ATTRIBUTE, objects.named("start-scripts")) outgoing.artifact(startScripts) }Registered: Wed Dec 31 11:36:14 UTC 2025 - Last Modified: Wed Jul 02 12:28:02 UTC 2025 - 1.9K bytes - Viewed (0) -
docs/smb3-features/04-directory-leasing-design.md
// First listing should hit the server long start1 = System.currentTimeMillis(); SmbFile[] files1 = dir.listFiles(); long time1 = System.currentTimeMillis() - start1; // Second listing should use cache (much faster) long start2 = System.currentTimeMillis(); SmbFile[] files2 = dir.listFiles(); long time2 = System.currentTimeMillis() - start2; assertEquals(files1.length, files2.length);Registered: Sat Dec 20 13:44:44 UTC 2025 - Last Modified: Sat Aug 16 02:53:50 UTC 2025 - 36.2K bytes - Viewed (0) -
docs/en/docs/advanced/events.md
# Lifespan Events { #lifespan-events } You can define logic (code) that should be executed before the application **starts up**. This means that this code will be executed **once**, **before** the application **starts receiving requests**. The same way, you can define logic (code) that should be executed when the application is **shutting down**. In this case, this code will be executed **once**, **after** having handled possibly **many requests**.Registered: Sun Dec 28 07:19:09 UTC 2025 - Last Modified: Wed Dec 17 20:41:43 UTC 2025 - 7.9K bytes - Viewed (0) -
architecture/build-execution-model.md
1. The client looks for a compatible idle daemon. If there isn't one, it starts a new daemon. 2. The client connects to the idle daemon and sends it a request to do some work. If the daemon is no longer running, the client starts again. 3. If the daemon is not able to run the request, for example it is already running a request or is shutting down, it rejects the request. The client starts again.
Registered: Wed Dec 31 11:36:14 UTC 2025 - Last Modified: Thu Jun 12 09:50:57 UTC 2025 - 907 bytes - Viewed (0)