Aleksey Savchuk
e2a6663ef6
All checks were successful
Vulncheck / Vulncheck (pull_request) Successful in 3m0s
Pre-commit hooks / Pre-commit (pull_request) Successful in 3m33s
Tests and linters / gopls check (pull_request) Successful in 4m29s
Tests and linters / Tests with -race (pull_request) Successful in 6m11s
Tests and linters / Run gofumpt (pull_request) Successful in 7m7s
DCO action / DCO (pull_request) Successful in 7m34s
Tests and linters / Staticcheck (pull_request) Successful in 9m23s
Tests and linters / Tests (pull_request) Successful in 9m30s
Build / Build Components (pull_request) Successful in 10m10s
Tests and linters / Lint (pull_request) Successful in 10m23s
Consider the following methods: - `(*Shard).collectExpiredTombstones` - `(*StorageEngines).processExpiredTombstones` - `(*Shard).HandleExpiredTombstones` All of them handle not tombstones but graves. `HandleExpiredTombstones` in fact deletes tombstones but it does it based on graves it received. So, rename all `...Tombstones` methods to `...Graves` method. It'll make future changes in the garbage collector behavior simpler. Also, rename all `...Locks` methods to `...LockObjects` because they handle not locks but lock objects. Signed-off-by: Aleksey Savchuk <a.savchuk@yadro.com> |
||
|---|---|---|
| .. | ||
| mode | ||
| container.go | ||
| control.go | ||
| control_test.go | ||
| count.go | ||
| delete.go | ||
| delete_test.go | ||
| errors.go | ||
| exists.go | ||
| gc.go | ||
| gc_internal_test.go | ||
| gc_test.go | ||
| get.go | ||
| get_test.go | ||
| head.go | ||
| head_test.go | ||
| id.go | ||
| info.go | ||
| inhume.go | ||
| inhume_test.go | ||
| list.go | ||
| list_test.go | ||
| lock.go | ||
| lock_test.go | ||
| metrics.go | ||
| metrics_test.go | ||
| mode.go | ||
| put.go | ||
| range.go | ||
| range_test.go | ||
| rebuild.go | ||
| refill_test.go | ||
| reload_test.go | ||
| select.go | ||
| shard.go | ||
| shard_test.go | ||
| shutdown_test.go | ||
| tree.go | ||
| writecache.go | ||