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

[FEA] Establish RAFT API contract #360

Closed
3 tasks done
cjnolet opened this issue Oct 12, 2021 · 5 comments
Closed
3 tasks done

[FEA] Establish RAFT API contract #360

cjnolet opened this issue Oct 12, 2021 · 5 comments
Assignees
Labels
EPIC These might span releases feature request New feature or request inactive-30d inactive-90d Public API

Comments

@cjnolet
Copy link
Member

cjnolet commented Oct 12, 2021

Tracking issue for updating the public API functions to adhere to the agreed-upon contract. This includes the ongoing refactor work kicked off by @divyegala.

  • Add handle and remove explicit stream
  • Use common storage / representation formats
  • Consistency in ordering of arguments (ins vs outs, etc...)
@cjnolet cjnolet added the feature request New feature or request label Oct 12, 2021
@github-actions
Copy link

github-actions bot commented Dec 1, 2021

This issue has been labeled inactive-30d due to no recent activity in the past 30 days. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed. This issue will be labeled inactive-90d if there is no activity in the next 60 days.

@cjnolet cjnolet added EPIC These might span releases and removed inactive-30d labels Dec 6, 2021
@github-actions
Copy link

This issue has been labeled inactive-30d due to no recent activity in the past 30 days. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed. This issue will be labeled inactive-90d if there is no activity in the next 60 days.

@cjnolet
Copy link
Member Author

cjnolet commented Mar 16, 2022

Marking the subtasks done here since we already have alignment on them. Remaining work will be completed in #535

@github-actions
Copy link

This issue has been labeled inactive-30d due to no recent activity in the past 30 days. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed. This issue will be labeled inactive-90d if there is no activity in the next 60 days.

@github-actions
Copy link

This issue has been labeled inactive-90d due to no recent activity in the past 90 days. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
EPIC These might span releases feature request New feature or request inactive-30d inactive-90d Public API
Projects
None yet
Development

No branches or pull requests

2 participants