/ DCO (pull_request) Successful in 1m17s
Details
/ Lint (pull_request) Successful in 2m36s
Details
/ Tests (1.19) (pull_request) Successful in 2m14s
Details
/ Tests (1.20) (pull_request) Successful in 6m0s
Details
Here is a scenario: 1. `resolveFrostFSErrors` is false. 2. The first object part was not written, which was signified in status. 3. The second part was written correctly. Client now thinks that the object is written even though it was not. In theory we could also return only status, but client-side splitting is not a single RPC, so it makes sense. Signed-off-by: Evgenii Stratonikov <e.stratonikov@yadro.com> |
||
---|---|---|
.. | ||
status | ||
accounting.go | ||
api.go | ||
client.go | ||
client_test.go | ||
common.go | ||
container.go | ||
container_delete.go | ||
container_eacl.go | ||
container_get.go | ||
container_list.go | ||
container_put.go | ||
container_set_eacl.go | ||
container_space.go | ||
doc.go | ||
errors.go | ||
errors_test.go | ||
netmap.go | ||
netmap_test.go | ||
object_delete.go | ||
object_get.go | ||
object_hash.go | ||
object_put.go | ||
object_put_raw.go | ||
object_put_single.go | ||
object_put_transformer.go | ||
object_search.go | ||
object_search_test.go | ||
response.go | ||
session.go |