Range failed on complex object
I ran that test several times on master (both node and sdk) and can't reproduce:
~/src/frostfs-sdk-go$ go test -count 1 -timeout 30s -v -run ^TestPool$ git.frostfs.info/TrueCloudLab/frostfs…
[#561] writecache: Make badger keys counting async
There's not much point in having a WriteBatch
for a single update. Update
can be used instead.
This was introduced by me but it doesn't really match what bbolt does internally via the Batch
…
Simplify writecache implementations
Do you have any specific ideas in mind?
I would recommend trying to implement something very simple, not using any existing key-value and without the need to iterate over the key space…
Potential confusion about
apistatus
error types' semantic equivalence
ok. The original bug is not more, so I'm closing. We can address the design question elsewhere.
Potential confusion about
apistatus
error types' semantic equivalence
[#598] Fix read-after-close bug in badger writecache
P.S.: soon nobody will be able to touch writecache code due to the complexity.
So let's create task to simplify?
Simplify writecache implementations
[#xx] Avoid manual management of files in tests
ale64bit
created branch cleanup/manual-files-in-testing in ale64bit/frostfs-node
2023-08-14 11:01:49 +00:00
ale64bit
pushed to cleanup/manual-files-in-testing at ale64bit/frostfs-node
2023-08-14 11:01:49 +00:00
ae8be495c8
[#xx] Avoid manual management of files in tests
[#xx] Just to trigger CI run
dfa7305b42
[#xx] Just to trigger CI run
376f03a445
[#598] Hold mode mutex when setting mode
ad87493c41
[#8] Bump required go version to go1.20
21800e9fcc
[#162] core: Move literals to constants
a5f51add25
[#162] ci: Add noliteral linter