Skip to content
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: add documentation for disperser v2 grpc api and related functions/structs #1104

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

samlaf
Copy link
Contributor

@samlaf samlaf commented Jan 13, 2025

Why are these changes needed?

The v2 interfaces are missing documentation, which makes it hard for intergration to interface with core. Adding some ad-hoc documentation here for thing that I needed to lookup today, but would be useful to do a uniform pass on the API to make sure its documentation is complete at some point.

Just learned about #1082, so therre might be some redundancy here. Probably should merge that one first (it's documents every more broadly) and then I'll rebase mine on top (I have more precise documentation for much fewer things).

Checks

  • I've made sure the tests are passing. Note that there might be a few flaky tests, in that case, please comment that they are not relevant.
  • I've checked the new test coverage and the coverage percentage didn't drop.
  • Testing Strategy
    • Unit tests
    • Integration tests
    • This PR is not tested :(

Comment on lines +29 to 31
// TODO: is this length always a power of 2? Are there any other characteristics that we should list? etc.
uint32 length = 4;
}
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does anyone know for this one?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes it's the padded length, always power of 2 (so maybe not really "actual degree/length" as commented above)

Comment on lines +19 to +21
// TODO: we should probably just force the data to be a multiple of 32 bytes.
// This would make the API and code simpler to read, and also allow the code
// to be auto-vectorized by the compiler (it probably isn't right now given the if inside the for loop).
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we do this? Really think it would greatly help devex.

@litt3 litt3 self-requested a review January 15, 2025 14:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants