minio-4.0.6.tar minio/Chart.yaml apiVersion: v1 appVersion: RELEASE.2022-05-08T23-50-31Z description: Multi-Cloud Object Storage home: https://min.io icon: https://min.io/resources/img/logo/MINIO_wordmark.png keywords: - minio - storage - object-storage - s3 - cluster maintainers: - email: ******@****.*** name: MinIO, Inc name: minio sources: - https://github.com/minio/minio version: 4.0.6 minio/values.yaml ## Provide a name in place of minio for `app:` labels ## nameOverride: "" ## Provide a name...

```

### Real-time 'status' for a batch job
```
mc batch status myminio/ E24HH4nNMcgY5taynaPfxu
●∙∙
Objects:        28766
Versions:       28766
Throughput:     3.0 MiB/s
Transferred:    406 MiB
Elapsed:        2m14.227222868s
CurrObjName:    share/doc/xml-core/examples/foo.xmlcatalogs
```

### 'describe' the batch job yaml.
```
mc batch describe myminio/ E24HH4nNMcgY5taynaPfxu
replicate:

  "durations" : [ {
    "testProject" : "nowInAndroidBuild",
    "linux" : 313,
    "windows" : 406,
    "macOs" : 246
  }, {
    "testProject" : "santaTrackerAndroidBuild",
    "linux" : 430,
    "windows" : 768,
    "macOs" : 423
  } ]
}, {

    maintainers:
    - email: ******@****.***
      name: MinIO, Inc
    name: minio
    sources:
    - https://github.com/minio/minio
    urls:
    - https://charts.min.io/helm-releases/minio-4.0.6.tgz
    version: 4.0.6
  - apiVersion: v1
    appVersion: RELEASE.2022-05-08T23-50-31Z
    created: "2024-10-11T14:15:09.763510175+02:00"
    description: Multi-Cloud Object Storage

headers are now properly handled as per the HTTP spec.  As a consequence, if
you had a client that was sending an invalid Content-Type or Accept header to
the API, in 1.2 you will either receive a 415 or 406 error.
The only client
this is known to affect is curl when you use -d with JSON but don't set a
content type, helpfully sends "application/x-www-urlencoded", which is not
correct.

    assertCached(false, 400)
    assertCached(false, 401)
    assertCached(false, 402)
    assertCached(false, 403)
    assertCached(true, 404)
    assertCached(true, 405)
    assertCached(false, 406)
    assertCached(false, 408)
    assertCached(false, 409)
    // the HTTP spec permits caching 410s, but the RI doesn't.
    assertCached(true, 410)
    assertCached(false, 411)
    assertCached(false, 412)

- If a client makes an API streaming requests and specifies an `application/json;as=Table` content type, the API server now responds with a 406 (Not Acceptable) error.

pkg syscall (freebsd-arm64), const SYS_KSEM_TRYWAIT = 403
pkg syscall (freebsd-arm64), const SYS_KSEM_TRYWAIT ideal-int
pkg syscall (freebsd-arm64), const SYS_KSEM_UNLINK = 406
pkg syscall (freebsd-arm64), const SYS_KSEM_UNLINK ideal-int
pkg syscall (freebsd-arm64), const SYS_KSEM_WAIT = 402
pkg syscall (freebsd-arm64), const SYS_KSEM_WAIT ideal-int

pkg syscall (darwin-arm64), const SYS_FCHOWN ideal-int
pkg syscall (darwin-arm64), const SYS_FCNTL = 92
pkg syscall (darwin-arm64), const SYS_FCNTL ideal-int
pkg syscall (darwin-arm64), const SYS_FCNTL_NOCANCEL = 406
pkg syscall (darwin-arm64), const SYS_FCNTL_NOCANCEL ideal-int
pkg syscall (darwin-arm64), const SYS_FDATASYNC = 187
pkg syscall (darwin-arm64), const SYS_FDATASYNC ideal-int

    * If the serialization type is application/vnd.kubernetes.protobuf, and protobuf marshaling is not implemented for the requested API resource type, a '406 Not Acceptable is returned'.
    * If the serialization type is 'application/json':
    * If serialization fails, and the original status code was an failure (e.g. 4xx or 5xx), the original status code will be returned.