-
Notifications
You must be signed in to change notification settings - Fork 376
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
docs: reword adr-013 and describe SubtreeRootThreshold
#1959
Conversation
Codecov Report
@@ Coverage Diff @@
## main #1959 +/- ##
=======================================
Coverage 21.21% 21.21%
=======================================
Files 121 121
Lines 13704 13704
=======================================
Hits 2907 2907
Misses 10509 10509
Partials 288 288
|
Why does it need to be renamed to two? Can't we just document the changes in the changelog |
It doesn't need to be renamed but I renamed b/c I thought it was misleading that the ADR was titled "zero padding". With this proposal, there will still be padding but there is just less padding than ADR-009. |
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.
due to the rename, its difficult to spot the rephrases, but its probably fine
I'm not blocking on renaming, but perhaps we should keep that to a separate PR?
Theoretically if you have a ridiculously large SubtreeRootThreshold there will be zero padding no matter how large the blob is. I actually don't mind renaming it to "reduced-padding" but I don't think the |
SubtreeRootThreshold
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.
nice! thanks for updating this
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.
Thank you! Left some comments
docs/architecture/adr-013-non-interactive-default-rules-for-zero-padding.md
Outdated
Show resolved
Hide resolved
docs/architecture/adr-013-non-interactive-default-rules-for-zero-padding.md
Outdated
Show resolved
Hide resolved
If the threshold is bigger than `MinSquareSize(blob)` then the blob will be aligned to the index of the `MinSquareSize(blob)`. This would prevent some blob size ranges to have higher padding than they had before this change. So the real new non-interactive default rules would be: | ||
|
||
Blobs start at an index that is equal to a multiple of the blob length divided by `MaxSquareSize` rounded up. If this index is larger than the `MinSquareSize` of the blob then the blob starts at the index of the `MinSquareSize`. | ||
Blobs start at an index that is equal to a multiple of the blob length divided by `MaxSquareSize` rounded up. If this index is larger than the `MinSquareSize(blob)` then the blob starts at the index that is a multiple of of the `MinSquareSize(blob)`. |
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.
Maybe we reference that where we explain the new non-interactive default rules? See my comment above
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.
Attempted to address via 4a4d336
please LMK what you think
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.
It is good. You are introducing subtree root width as a variable name, but explaining what it means in words may also make sense as it is the first mention in the ADR.
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.
Was this footnote not easy to discover? or are there other words you would use to define it?
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.
I'm going to merge b/c two approvals but happy to amend the footnote or describe it differently in a follow-up PR. Thanks for your reviews!
* docs: add section to adr-013 * update links * revert: ADR name change * revert: hyphen change * improve: godoc * Address @nashqueue feedback
* docs: add section to adr-013 * update links * revert: ADR name change * revert: hyphen change * improve: godoc * Address @nashqueue feedback
Closes #1877
Closes #1607
Description
MaxSquareSize
withSubtreeRootThreshold
where applicable.