test: Generate correct IDs for tests #106
No reviewers
Labels
No labels
P0
P1
P2
P3
good first issue
Infrastructure
blocked
bug
config
discussion
documentation
duplicate
enhancement
go
help wanted
internal
invalid
kludge
observability
perfomance
question
refactoring
wontfix
No milestone
No project
No assignees
5 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-api-go#106
Loading…
Reference in a new issue
No description provided.
Delete branch "a-savchuk/frostfs-api-go:test/generate-ids"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Some tests are using invalid IDs, such as this one, which isn't 32 bytes long as required by the FrostFS protocol. While this may not be the direct responsibility of the API repository, I believe we should avoid using test IDs that don't reflect real-world scenarios.
This issue was originally highlighted here.
Signed-off-by: Aleksey Savchuk a.savchuk@yadro.com
f9ad60d418
to3f35301340
Signature
could also be changed -- see how we marshal the key and signature (33 and 64 bytes)Also, the scheme could be constant (exactly not to deal with non-constant lengths)
3f35301340
to7fd808b317
Tbh, I couldn't find an information about key and signature sizes there but found it in
frostfs-crypto
repository.I've also updated the test data generation in some other places.
7fd808b317
to5e7a15f3f1
Could you please elaborate in the commit message what was wrong with
ID
s in tests before?@ -4,6 +4,8 @@ import (
"math/rand"
"time"
crand "crypto/rand"
Please make no empty lines between stdlib imports
Fixed
5e7a15f3f1
to6052aecd0f
6052aecd0f
to9c5e32a183