op-node: Fixed Integers in channel frame header#3126
Conversation
|
|
This PR changes implementation code, but doesn't include a changeset. Did you forget to add one? |
19f9215 to
d0d9a61
Compare
bc6cd91 to
6ab970c
Compare
d0d9a61 to
6f9926c
Compare
|
Hey @trianglesphere! This PR has merge conflicts. Please fix them before continuing review. |
6ab970c to
c5cb400
Compare
6f9926c to
7539390
Compare
c5cb400 to
ba2bb47
Compare
|
Hey @trianglesphere! This PR has merge conflicts. Please fix them before continuing review. |
ba2bb47 to
0b93989
Compare
|
Hey @trianglesphere! This PR has merge conflicts. Please fix them before continuing review. |
b1b9914 to
4b53a5c
Compare
4b53a5c to
7ab20bb
Compare
This mainly modifies the channel_frame, but has some knock on effects as the width of some of the fields have been reduced. The channel frame code is also changed more than I expected due to differences in API of working with fixed int vs uvarints in go. Otherwise the code reads very similarly with using Reader/Writer APIs.
7ab20bb to
a694f3d
Compare
a694f3d to
1212d38
Compare
protolambda
left a comment
There was a problem hiding this comment.
looks good, but not approving just yet to avoid auto-merge, one nit style fix first.
|
This PR has been added to the merge queue, and will be merged soon. |
|
This PR is next in line to be merged, and will be merged as soon as checks pass. |
* goals for fixed int * op-node: Fixed integer sizes in the channel header This mainly modifies the channel_frame, but has some knock on effects as the width of some of the fields have been reduced. The channel frame code is also changed more than I expected due to differences in API of working with fixed int vs uvarints in go. Otherwise the code reads very similarly with using Reader/Writer APIs. * op-node: fix frame unmarshal func to return correct err * specs: update frame format specs * Update op-node/rollup/derive/channel_bank_test.go Co-authored-by: protolambda <proto@protolambda.com> Co-authored-by: Matthew Slipper <me@matthewslipper.com>
* goals for fixed int * op-node: Fixed integer sizes in the channel header This mainly modifies the channel_frame, but has some knock on effects as the width of some of the fields have been reduced. The channel frame code is also changed more than I expected due to differences in API of working with fixed int vs uvarints in go. Otherwise the code reads very similarly with using Reader/Writer APIs. * op-node: fix frame unmarshal func to return correct err * specs: update frame format specs * Update op-node/rollup/derive/channel_bank_test.go Co-authored-by: protolambda <proto@protolambda.com> Co-authored-by: Matthew Slipper <me@matthewslipper.com>
* goals for fixed int * op-node: Fixed integer sizes in the channel header This mainly modifies the channel_frame, but has some knock on effects as the width of some of the fields have been reduced. The channel frame code is also changed more than I expected due to differences in API of working with fixed int vs uvarints in go. Otherwise the code reads very similarly with using Reader/Writer APIs. * op-node: fix frame unmarshal func to return correct err * specs: update frame format specs * Update op-node/rollup/derive/channel_bank_test.go Co-authored-by: protolambda <proto@protolambda.com> Co-authored-by: Matthew Slipper <me@matthewslipper.com>
Description
This switches the channel frame header over to using fixed integers. This avoids a circular
dependency when filling the serialized frame up to a maximum size. The circular dependency
is caused by the frame data length being a
uvarintwhich can vary in size when serialized.Metadata