- Sort Score
- Num 10 results
- Language All
Results 1 - 10 of 248 for dangling (0.09 seconds)
-
.github/workflows/run-mint.sh
docker volume prune -f || true docker volume rm $(docker volume ls -f dangling=true) || true ## change working directory cd .github/workflows/mint ## always pull latest docker pull docker.io/minio/mint:edge docker-compose -f minio-${MODE}.yaml up -d sleep 1m docker system prune -f || true docker volume prune -f || true docker volume rm $(docker volume ls -q -f dangling=true) || trueCreated: Sun Apr 05 19:28:12 GMT 2026 - Last Modified: Mon Jan 20 14:49:07 GMT 2025 - 1.9K bytes - Click Count (0) -
buildscripts/minio-upgrade.sh
docker volume rm ${volume} || true done docker volume prune -f docker system prune -f || true docker volume prune -f || true docker volume rm $(docker volume ls -q -f dangling=true) || true } verify_checksum_after_heal() { local sum1 sum1=$(curl -s "$2" | sha256sum) mc admin heal --json -r "$1" >/dev/null # test after healing local sum1_heal sum1_heal=$(curl -s "$2" | sha256sum)Created: Sun Apr 05 19:28:12 GMT 2026 - Last Modified: Mon Apr 21 16:24:31 GMT 2025 - 2.8K bytes - Click Count (0) -
.github/workflows/multipart/migrate.sh
for volume in $(docker volume ls -q | grep minio); do docker volume rm ${volume} || true done docker system prune -f || true docker volume prune -f || true docker volume rm $(docker volume ls -q -f dangling=true) || true } cleanup if [ ! -f ./mc ]; then wget --quiet -O mc https://dl.minio.io/client/mc/release/linux-amd64/mc && chmod +x mc fi export RELEASE=RELEASE.2023-08-29T23-07-35ZCreated: Sun Apr 05 19:28:12 GMT 2026 - Last Modified: Mon May 27 19:17:46 GMT 2024 - 4.3K bytes - Click Count (0) -
.github/workflows/mint.yml
docker rmi -f quay.io/minio/minio:${{ steps.vars.outputs.sha_short }} docker system prune -f || true docker volume prune -f || trueCreated: Sun Apr 05 19:28:12 GMT 2026 - Last Modified: Wed Apr 09 14:28:39 GMT 2025 - 2.9K bytes - Click Count (0) -
okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/http/HttpHeaders.kt
Created: Fri Apr 03 11:42:14 GMT 2026 - Last Modified: Tue Jan 27 09:00:39 GMT 2026 - 7.2K bytes - Click Count (0) -
cmd/peer-s3-server.go
res.Before.Drives = append(res.Before.Drives, madmin.HealDriveInfo{ UUID: "", Endpoint: localDrives[i].Endpoint().String(), State: beforeState[i], }) } // check dangling and delete bucket only if its not a meta bucket if !isMinioMetaBucketName(bucket) && !isAllBucketsNotFound(errs) && opts.Remove { g := errgroup.WithNErrs(len(localDrives)) for index := range localDrives {
Created: Sun Apr 05 19:28:12 GMT 2026 - Last Modified: Fri Aug 29 02:39:48 GMT 2025 - 8.2K bytes - Click Count (0) -
docs/en/docs/tutorial/handling-errors.md
# Handling Errors { #handling-errors } There are many situations in which you need to notify an error to a client that is using your API. This client could be a browser with a frontend, a code from someone else, an IoT device, etc. You could need to tell the client that: * The client doesn't have enough privileges for that operation. * The client doesn't have access to that resource. * The item the client was trying to access doesn't exist. * etc.Created: Sun Apr 05 07:19:11 GMT 2026 - Last Modified: Thu Mar 05 18:13:19 GMT 2026 - 8.9K bytes - Click Count (0) -
docs/es/docs/tutorial/handling-errors.md
# Manejo de Errores { #handling-errors } Existen muchas situaciones en las que necesitas notificar un error a un cliente que está usando tu API. Este cliente podría ser un navegador con un frontend, un código de otra persona, un dispositivo IoT, etc. Podrías necesitar decirle al cliente que: * El cliente no tiene suficientes privilegios para esa operación. * El cliente no tiene acceso a ese recurso. * El ítem al que el cliente intentaba acceder no existe.Created: Sun Apr 05 07:19:11 GMT 2026 - Last Modified: Thu Mar 19 18:15:55 GMT 2026 - 9.6K bytes - Click Count (0) -
docs/tr/docs/tutorial/handling-errors.md
# Hataları Yönetme { #handling-errors } API’nizi kullanan bir client’a hata bildirmek zorunda olduğunuz pek çok durum vardır. Bu client; frontend’i olan bir tarayıcı, başka birinin yazdığı bir kod, bir IoT cihazı vb. olabilir. Client’a şunları söylemeniz gerekebilir: * Client’ın bu işlem için yeterli yetkisi yok. * Client’ın bu kaynağa erişimi yok. * Client’ın erişmeye çalıştığı öğe mevcut değil. * vb.Created: Sun Apr 05 07:19:11 GMT 2026 - Last Modified: Fri Mar 20 07:53:17 GMT 2026 - 9.7K bytes - Click Count (0) -
docs/zh/docs/tutorial/handling-errors.md
# 处理错误 { #handling-errors } 某些情况下,需要向使用你的 API 的客户端返回错误提示。 这里所谓的客户端包括前端浏览器、他人的代码、物联网设备等。 你可能需要告诉客户端: - 客户端没有执行该操作的权限 - 客户端没有访问该资源的权限 - 客户端要访问的项目不存在 - 等等 遇到这些情况时,通常要返回 **4XX**(400 至 499)**HTTP 状态码**。 这与表示请求成功的 **2XX**(200 至 299)HTTP 状态码类似。那些“200”状态码表示某种程度上的“成功”。 而 **4XX** 状态码表示客户端发生了错误。 大家都知道**「404 Not Found」**错误,还有调侃这个错误的笑话吧? ## 使用 `HTTPException` { #use-httpexception }Created: Sun Apr 05 07:19:11 GMT 2026 - Last Modified: Fri Mar 20 17:06:37 GMT 2026 - 8.2K bytes - Click Count (0)