Fix/Actualize notary requests parsing #268
Labels
No labels
P0
P1
P2
P3
badger
frostfs-adm
frostfs-cli
frostfs-ir
frostfs-lens
frostfs-node
good first issue
triage
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
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-node#268
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/notary-preparator-is-outdated"
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?
After
75d7891ca1
neo-go
does claim that an empty invocation script is the only way tofill missing signature for unsigned notary requests. The new notary actor
does it that way and, therefore, breaks notary request parsing by the
Alphabet because of skipping any request that is not filled with a dummy (64
zeros) invocation script. Support both way. The "Dummy" approach will be
dropped later.
Signed-off-by: Pavel Karpy p.karpy@yadro.com
157086e88a
to3a3e0ac615
3a3e0ac615
to2044803f8e
2044803f8e
to6591e97430
6591e97430
to8178c04eae
8178c04eae
to4f5f832137