- Sort Score
- Num 10 results
- Language All
Results 1 - 10 of 56 for unmount (0.05 seconds)
The search processing time has exceeded the limit. The displayed results may be partial.
-
docs/en/docs/advanced/sub-applications.md
{* ../../docs_src/sub_applications/tutorial001_py39.py hl[11, 14:16] *} ### Mount the sub-application { #mount-the-sub-application } In your top-level application, `app`, mount the sub-application, `subapi`. In this case, it will be mounted at the path `/subapi`: {* ../../docs_src/sub_applications/tutorial001_py39.py hl[11, 19] *}Created: Sun Dec 28 07:19:09 GMT 2025 - Last Modified: Wed Dec 17 20:41:43 GMT 2025 - 3K bytes - Click Count (0) -
internal/ioutil/hardlimitreader.go
func HardLimitReader(r io.Reader, n int64) io.Reader { return &HardLimitedReader{r, n} } // A HardLimitedReader reads from R but limits the amount of // data returned to just N bytes. Each call to Read // updates N to reflect the new amount remaining. // Read returns EOF when N <= 0 or when the underlying R returns EOF. type HardLimitedReader struct { R io.Reader // underlying reader
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Sun Sep 28 20:59:21 GMT 2025 - 2K bytes - Click Count (0) -
CHANGELOG/CHANGELOG-1.33.md
- [Action Required] CSI drivers that call IsLikelyNotMountPoint should not assume false means that the path is a mount point. Each CSI driver needs to make sure correct usage of return value of IsLikelyNotMountPoint because if the file is an irregular file but not a mount point is acceptable ([#129370](https://github.com/kubernetes/kubernetes/pull/129370), [@andyzhangx](https://github.com/andyzhangx)) [SIG Storage and Windows]
Created: Fri Dec 26 09:05:12 GMT 2025 - Last Modified: Wed Dec 10 01:15:24 GMT 2025 - 334.8K bytes - Click Count (0) -
docs/en/docs/advanced/wsgi.md
# Including WSGI - Flask, Django, others { #including-wsgi-flask-django-others } You can mount WSGI applications as you saw with [Sub Applications - Mounts](sub-applications.md){.internal-link target=_blank}, [Behind a Proxy](behind-a-proxy.md){.internal-link target=_blank}. For that, you can use the `WSGIMiddleware` and use it to wrap your WSGI application, for example, Flask, Django, etc. ## Using `WSGIMiddleware` { #using-wsgimiddleware }Created: Sun Dec 28 07:19:09 GMT 2025 - Last Modified: Wed Dec 17 20:41:43 GMT 2025 - 1.2K bytes - Click Count (0) -
docs/ru/llm-prompt.md
* worker: воркер * lifespan: lifespan (do not translate when it's about lifespan events, but translate as `жизненный цикл` or `срок жизни` in other cases) * mount (verb): монтировать * mount (noun): точка монтирования / mount (keep in English if it's a FastAPI keyword) * plugin: плагин * plug-in: плагин * full stack: full stack (do not translate) * full-stack: full-stack (do not translate)
Created: Sun Dec 28 07:19:09 GMT 2025 - Last Modified: Mon Oct 06 11:09:58 GMT 2025 - 6K bytes - Click Count (0) -
android/guava-tests/test/com/google/common/io/FileBackedOutputStreamTest.java
/** * Test that verifies the resource leak fix for <a * href="https://github.com/google/guava/issues/5756">Issue #5756</a>. * * <p>This test covers a scenario where we write a smaller amount of data first, then write a * large amount that crosses the threshold (transitioning from "not at threshold" to "over the * threshold"). (We then write some more afterward.) This differs from the existing
Created: Fri Dec 26 12:43:10 GMT 2025 - Last Modified: Thu Oct 30 16:30:29 GMT 2025 - 6.7K bytes - Click Count (0) -
docs/en/docs/deployment/concepts.md
And multiple processes normally **don't share any memory**. This means that each running process has its own things, variables, and memory. And if you are consuming a large amount of memory in your code, **each process** will consume an equivalent amount of memory. ### Server Memory { #server-memory }Created: Sun Dec 28 07:19:09 GMT 2025 - Last Modified: Sun Aug 31 09:15:41 GMT 2025 - 18.6K bytes - Click Count (1) -
docs/en/docs/deployment/docker.md
you will have a more or less well-defined, stable, and limited amount of memory consumed by each of those containers (more than one if they are replicated). And then you can set those same memory limits and requirements in your configurations for your container management system (for example in **Kubernetes**). That way it will be able to **replicate the containers** in the **available machines** taking into account the amount of memory needed by them, and the amount available in the machines...
Created: Sun Dec 28 07:19:09 GMT 2025 - Last Modified: Sat Sep 20 12:58:04 GMT 2025 - 29.5K bytes - Click Count (1) -
docs/chroot/README.md
chmod +x /mnt/export/${USER}/bin/minio ``` Alternatively, if you have an existing legacy binary, you can still use it, but note that it will not receive updates. Bind your `proc` mount to the target chroot directory ``` sudo mount --bind /proc /mnt/export/${USER}/proc ``` ## 3. Run Standalone MinIO in Chroot ### GNU/Linux ```shCreated: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Wed Oct 15 17:29:55 GMT 2025 - 2.2K bytes - Click Count (0) -
src/cmd/asm/internal/asm/parse.go
tok := p.next() ext = tok.String() } if p.peek() == lex.LSH { // parses left shift amount applied after extension: <<Amount p.get(lex.LSH) tok := p.get(scanner.Int) amount, err := strconv.ParseInt(tok.String(), 10, 16) if err != nil { p.errorf("parsing left shift amount: %s", err) } num = int16(amount) } else if p.peek() == '[' { // parses an element: [Index] p.get('[')
Created: Tue Dec 30 11:13:12 GMT 2025 - Last Modified: Wed Nov 12 03:59:40 GMT 2025 - 37.3K bytes - Click Count (0)