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

Automated Protos Update #230

Merged
merged 2 commits into from
May 9, 2024
Merged

Automated Protos Update #230

merged 2 commits into from
May 9, 2024

Conversation

github-actions[bot]
Copy link
Contributor

This is an auto-generated PR to update proto definitions. Check the commits to see which repos and commits are responsible for the changes

@github-actions github-actions bot requested a review from a team as a code owner April 27, 2024 16:34
@github-actions github-actions bot requested review from njooma and purplenicole730 and removed request for a team April 27, 2024 16:34
@github-actions github-actions bot requested a review from stuqdog April 27, 2024 16:34
@github-actions github-actions bot force-pushed the workflow/update-protos branch 3 times, most recently from ad52b6e to 16e4193 Compare May 1, 2024 16:27
penguinland added a commit that referenced this pull request May 9, 2024
This turned out to be two problems combined! 1) update the SDK to use a more recent version of the protobufs in the API repo, and then 2) remove the `Status` RPC from the boards. The PR isn't quite done: I'm unsure how this should interact with #230, which is where the compiled version of the updated protos is. but the rest I think is ready for a look.

Updating the protobufs was harder than I expected: viamrobotics/api#470 (unrelated to boards) added a new type that had not been used previously, which meant that getting it to work required updating CMakeLists.txt to include the Google libraries for the new type.

Changes to boards:
- `get_status` doesn't exist any more. You can get the standard status from a component the same way you would for a motor, but there isn't a special board-specific one any more.
- In the component status you _can_ get, analog and digital interrupt values are stored as ints, not wrappers around ints. No need to unwrap.
- `get_analog_names` and `get_digital_interrupt_names` can't easily be implemented any more. They don't exist in the Flutter and TypeScript SDKs, and are hopefully being removed from the Go and Python SDKs soon (they have a purpose on the server side, but no obvious use on the client side, so probably shouldn't be in these SDKs). So, I removed them. 
- Similarly, I removed `get_analog_readers` and `get_digital_interrupts`, as they're not present in the Go SDK and would be very hard to implement without the old status.
@penguinland
Copy link
Member

Now that #231 has been merged into here, we need to get this PR merged into the main branch. @stuqdog, what can I help with on this?

@stuqdog stuqdog merged commit be72b3d into main May 9, 2024
3 checks passed
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.

3 participants