- Sort Score
- Result 10 results
- Languages All
Results 171 - 180 of 715 for tunnin (0.09 sec)
-
.github/workflows/mint/minio-compress-encrypt.yaml
healthcheck: test: ["CMD", "mc", "ready", "local"] interval: 5s timeout: 5s retries: 5 # starts 4 docker containers running minio server instances. # using nginx reverse proxy, load balancing, you can access # it through port 9000. services: minio1: <<: *minio-common hostname: minio1 volumes: - cdata1-1:/cdata1
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Fri Nov 03 21:18:18 UTC 2023 - 1.7K bytes - Viewed (0) -
.github/workflows/mint/minio-resiliency.yaml
MINIO_DRIVE_MAX_TIMEOUT: "5s" healthcheck: test: ["CMD", "mc", "ready", "local"] interval: 5s timeout: 5s retries: 5 # starts 4 docker containers running minio server instances. # using nginx reverse proxy, load balancing, you can access # it through port 9000. services: minio1: <<: *minio-common hostname: minio1 volumes: - rdata1-1:/rdata1
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Wed May 22 23:07:14 UTC 2024 - 1.7K bytes - Viewed (0) -
.github/workflows/multipart/docker-compose-site1.yaml
x-minio-common: &minio-common image: quay.io/minio/minio:${RELEASE} command: server http://site1-minio{1...4}/data{1...2} environment: - MINIO_PROMETHEUS_AUTH_TYPE=public - CI=true # starts 4 docker containers running minio server instances. # using nginx reverse proxy, load balancing, you can access # it through port 9000. services: site1-minio1: <<: *minio-common hostname: site1-minio1 volumes:
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Sat Sep 30 10:13:56 UTC 2023 - 1.5K bytes - Viewed (0) -
docs/en/docs/advanced/events.md
You could load it at the top level of the module/file, but that would also mean that it would **load the model** even if you are just running a simple automated test, then that test would be **slow** because it would have to wait for the model to load before being able to run an independent part of the code.
Registered: Sun Nov 03 07:19:11 UTC 2024 - Last Modified: Mon Oct 28 10:36:22 UTC 2024 - 7.6K bytes - Viewed (0) -
docs/fr/docs/deployment/manually.md
```console $ uvicorn main:app --host 0.0.0.0 --port 80 <span style="color: green;">INFO</span>: Uvicorn running on http://0.0.0.0:80 (Press CTRL+C to quit) ``` </div> //// //// tab | Hypercorn <div class="termy"> ```console $ hypercorn main:app --bind 0.0.0.0:80 Running on 0.0.0.0:8080 over http (CTRL + C to quit) ``` </div> //// /// warning
Registered: Sun Nov 03 07:19:11 UTC 2024 - Last Modified: Tue Aug 06 04:48:30 UTC 2024 - 5.3K bytes - Viewed (0) -
guava-gwt/src-super/com/google/common/util/concurrent/super/com/google/common/util/concurrent/AggregateFutureState.java
extends AbstractFuture.TrustedFuture<OutputT> { // Lazily initialized the first time we see an exception; not released until all the input futures // & this future completes. Released when the future releases the reference to the running state private @Nullable Set<Throwable> seenExceptions = null; private int remaining; AggregateFutureState(int remainingFutures) { this.remaining = remainingFutures; }
Registered: Fri Nov 01 12:43:10 UTC 2024 - Last Modified: Thu Dec 08 20:30:27 UTC 2022 - 1.7K bytes - Viewed (0) -
okhttp/src/main/kotlin/okhttp3/Authenticator.kt
* ## Preemptive Authentication * * To make HTTPS calls using an HTTP proxy server OkHttp must first negotiate a connection with * the proxy. This proxy connection is called a "TLS Tunnel" and is specified by * [RFC 2817][1]. The HTTP CONNECT request that creates this tunnel connection is special: it * does not participate in any [interceptors][Interceptor] or [event listeners][EventListener]. It
Registered: Fri Nov 01 11:42:11 UTC 2024 - Last Modified: Mon Jan 08 01:13:22 UTC 2024 - 5.5K bytes - Viewed (0) -
CHANGELOG.md
_2022-06-08_ * Fix: Change how `H2_PRIOR_KNOWLEDGE` works with HTTP proxies. Previously OkHttp assumed the proxy itself was a prior knowledge HTTP/2 server. With this update, OkHttp attempts a `CONNECT` tunnel just as it would with HTTPS. For prior knowledge with proxies OkHttp's is now consistent with these curl arguments: ``` curl \ --http2-prior-knowledge \ --proxy localhost:8888 \
Registered: Fri Nov 01 11:42:11 UTC 2024 - Last Modified: Thu Apr 18 01:31:39 UTC 2024 - 21.4K bytes - Viewed (0) -
docs/pt/docs/fastapi-cli.md
<span style="background-color:#C4A000"><font color="#2E3436">│ │</font></span> <span style="background-color:#C4A000"><font color="#2E3436">│ Running in development mode, for production use: │</font></span> <span style="background-color:#C4A000"><font color="#2E3436">│ │</font></span>
Registered: Sun Nov 03 07:19:11 UTC 2024 - Last Modified: Tue Aug 06 04:48:30 UTC 2024 - 6.4K bytes - Viewed (0) -
ci/official/utilities/setup_macos.sh
echo 'sure they are present on your system and try again.' exit 1 fi # "TFCI_MACOS_BAZEL_TEST_DIR_PATH" specifies the directory that Bazel should use # when running tests. Each test will be executed in a separate subdirectory # inside this directory. TF Mac builds need ~150 GB of disk space to be able to # run all the tests. Since TFCI Mac VMs execute Bazel test commands in a
Registered: Tue Nov 05 12:39:12 UTC 2024 - Last Modified: Thu Feb 15 15:23:28 UTC 2024 - 6.2K bytes - Viewed (0)