-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature/stream start, finish #111
base: feature/ReplicatorOffboarding
Are you sure you want to change the base?
Conversation
@@ -170,4 +170,5 @@ const ( | |||
ByteSize VarSize = 1 | |||
ShortSize VarSize = 2 | |||
IntSize VarSize = 4 | |||
LongSize VarSize = 8 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
usually, we use an array of IntSize
for uint64/int64
sdk/streamingv2_schema.go
Outdated
newArrayAttribute("maxFee", IntSize), | ||
newArrayAttribute("deadline", IntSize), | ||
newArrayAttribute("driveKey", ByteSize), | ||
newScalarAttribute("expectedUploadSize", LongSize), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
look at other uint64
fields (maxFee
, deadline
, etc). They use IntSize
array for it. So:
newArrayAttribute("expectedUploadSize", IntSize)
sdk/streamingv2_transaction.go
Outdated
} | ||
|
||
func (tx *StreamStartTransaction) String() string { | ||
return "" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
forgotten implementation?
maxFee: [uint]; | ||
deadline: [uint]; | ||
driveKey: [ubyte]; | ||
expectedUploadSize: uint64; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ulong
. But let follow other transaction and use [uint]
.:D
No description provided.