- Sort Score
- Result 10 results
- Languages All
Results 91 - 100 of 321 for topk (0.16 sec)
-
compat/maven-compat/src/test/java/org/apache/maven/artifact/resolver/DefaultArtifactResolverTest.java
createLocalArtifact("h", "1.0"); artifactResolver.resolveTransitively( Collections.singleton(g), projectArtifact, remoteRepositories(), localRepository(), null); // we want to see all top-level thread groups ThreadGroup tg = Thread.currentThread().getThreadGroup(); while (tg.getParent() == null) { tg = tg.getParent(); }
Registered: Sun Dec 28 03:35:09 UTC 2025 - Last Modified: Fri Mar 21 04:56:21 UTC 2025 - 3.1K bytes - Viewed (0) -
docs/en/docs/advanced/using-request-directly.md
## Details about the `Request` object { #details-about-the-request-object } As **FastAPI** is actually **Starlette** underneath, with a layer of several tools on top, you can use Starlette's <a href="https://www.starlette.dev/requests/" class="external-link" target="_blank">`Request`</a> object directly when you need to.Registered: Sun Dec 28 07:19:09 UTC 2025 - Last Modified: Wed Dec 17 20:41:43 UTC 2025 - 2.4K bytes - Viewed (0) -
src/main/webapp/js/admin/adminlte.min.js
.css("height",a.window-(a.header+a.footer));else if(i<=a.footer)if(!1===s){var d=a.header-o;t.css("bottom",a.footer-i).css("top",d>=0?d:0),r.css("height",a.window-(a.footer-i))}else t.css("bottom",a.footer);else o<=a.header?!1===l?(t.css("top",a.header-o),r.css("height",a.window-(a.header-o))):t.css("top",a.header):!1===l?(t.css("top",0),r.css("height",a.window)):t.css("top",a.header);s&&l?(r.css("height","100%"),t.css("height","")):(s||l)&&(r.css("height","100%"),r.css("height",""))}},t._fixHeight=function(){var...
Registered: Sat Dec 20 09:19:18 UTC 2025 - Last Modified: Sat Oct 26 01:49:09 UTC 2024 - 45.3K bytes - Viewed (0) -
okhttp/src/jvmTest/kotlin/okhttp3/CallTest.kt
.addHeader("Connection", "Close") .addHeader("Retry-After", "1") .body("You took too long!") .onResponseEnd(ShutdownConnection) .build(), ) val request = Request(server.url("/")) val response = client.newCall(request).execute() assertThat(response.body.string()).isEqualTo("You took too long!") } @Test fun requestBodyRetransmittedOnClientRequestTimeout() {
Registered: Fri Dec 26 11:42:13 UTC 2025 - Last Modified: Tue Nov 04 19:13:52 UTC 2025 - 147.4K bytes - Viewed (0) -
samples/tlssurvey/src/main/kotlin/okhttp3/survey/RunSurvey.kt
Registered: Fri Dec 26 11:42:13 UTC 2025 - Last Modified: Wed Mar 19 19:25:20 UTC 2025 - 3.5K bytes - Viewed (0) -
docs/en/docs/how-to/custom-request-and-route.md
In this example, the *path operations* under the `router` will use the custom `TimedRoute` class, and will have an extra `X-Response-Time` header in the response with the time it took to generate the response:
Registered: Sun Dec 28 07:19:09 UTC 2025 - Last Modified: Wed Dec 10 08:55:32 UTC 2025 - 4.6K bytes - Viewed (0) -
docs/en/docs/management.md
Some of the tasks they can perform include: * Adding labels to PRs. * Editing PR titles. * Adding commits on top of PRs to tweak them. * Mark answers in GitHub Discussions questions, etc. * Merge some specific types of PRs.
Registered: Sun Dec 28 07:19:09 UTC 2025 - Last Modified: Wed Jul 31 14:09:15 UTC 2024 - 1.7K bytes - Viewed (0) -
docs/pt/docs/advanced/behind-a-proxy.md
E também é usado internamente ao montar sub-aplicações. Ter um proxy com um prefixo de path removido, nesse caso, significa que você poderia declarar um path em `/app` no seu código, mas então você adiciona uma camada no topo (o proxy) que colocaria sua aplicação **FastAPI** sob um path como `/api/v1`. Nesse caso, o path original `/app` seria servido em `/api/v1/app`. Embora todo o seu código esteja escrito assumindo que existe apenas `/app`.
Registered: Sun Dec 28 07:19:09 UTC 2025 - Last Modified: Wed Dec 17 20:41:43 UTC 2025 - 17.2K bytes - Viewed (0) -
fess-crawler/src/test/resources/ajax/js/jquery-2.1.1.min.js
t:function(a,b,c){var d,e,f,g,h,i,j,k=n.css(a,"position"),l=n(a),m={};"static"===k&&(a.style.position="relative"),h=l.offset(),f=n.css(a,"top"),i=n.css(a,"left"),j=("absolute"===k||"fixed"===k)&&(f+i).indexOf("auto")>-1,j?(d=l.position(),g=d.top,e=d.left):(g=parseFloat(f)||0,e=parseFloat(i)||0),n.isFunction(b)&&(b=b.call(a,c,h)),null!=b.top&&(m.top=b.top-h.top+g),null!=b.left&&(m.left=b.left-h.left+e),"using"in b?b.using.call(a,m):l.css(m)}},n.fn.extend({offset:function(a){if(arguments.length)return...Registered: Sat Dec 20 11:21:39 UTC 2025 - Last Modified: Sun Oct 11 02:16:55 UTC 2015 - 82.3K bytes - Viewed (0) -
impl/maven-core/src/test/java/org/apache/maven/lifecycle/internal/stub/AboutTheStubs.html
The most important stubs are: LifecycleExecutionPlanCalculatorStub ProjectDependencyGraphStub Since they define the primary structure of the project/build. The stubs define three top-level targets that are defined in LifecycleTaskSegmentCalculatorStub; clean, aggr and install. "aggr" is an aggregating task while clean and install are lifecyclephases. There will be three items in the task list for this dataset.
Registered: Sun Dec 28 03:35:09 UTC 2025 - Last Modified: Fri Oct 25 12:31:46 UTC 2024 - 2.3K bytes - Viewed (0)