-
Notifications
You must be signed in to change notification settings - Fork 47
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
Allow distinct clearing price per lease duration bucket #142
Conversation
2245fbf
to
6940df3
Compare
I think this is ready for review now? |
Yes, has been for a while. |
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.
First pass. Main question is whether we can avoid breaking the API.
60fc034
to
b830718
Compare
I was able to make everything non-breaking! |
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.
Non-breaking changes look good on first pass!
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.
Great work on this PR! The latest version reads well to me.
Also needs a rebase!
812fc13
to
37793f9
Compare
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.
Awesome, this turned out very clean in the end 👌
Only nit from me is that I think we should make deprecated fields more clear by removing all but the deprecated message from their doc.
37793f9
to
47b3898
Compare
Rebased and addressed all comments. Even though this is ready to be merged now, I think we should wait until the server part is close to being merged as well. |
47b3898
to
32a51a3
Compare
32a51a3
to
fb68cd8
Compare
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.
Re-ACK ✅
fb68cd8
to
f0d659c
Compare
b626b3d
to
1ca3245
Compare
Because the batch Versions are in the order package, the use of order.DefaultVersion is confusing and not clear to be related to the version of the _batch_, just from its name. We fix that by renaming the versions of the batch.
Even though there still only is one batch version, we want to properly encode/decode it as a preparation for future version changes.
Because the order/lease duration is now governed by the lease durations, the maximum order duration is no longer needed.
We add a new order version that is allowed to submit lease durations outside of the default/legacy 2016 block duration. No new fields are added, so nothing changes in the serialization or the digest. This version only signals that the client is able to process batch requests with multiple duration buckets.
1ca3245
to
10c2ff1
Compare
Replaced by #199. |
…tweak monitoring/dashboards: don't specify an explicit datasource
This PR contains the client part of the change to switch over to distinct lease duration buckets for batches.
UPDATE: Made this non-breaking. Clients with batch version
0
won't be able to submit orders with a lease duration != 2016.UPDATE2: Depends on #193 which was split off to make the server changes easier to split into multiple PRs.