-
Notifications
You must be signed in to change notification settings - Fork 31
Implement V2 transport interface, fallbacks, and migrate hostcmd #275
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
Open
esnguyen
wants to merge
1
commit into
google:main
Choose a base branch
from
esnguyen:migration-phase1
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+240
−37
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
What's the reason for using the
libhoth_send_request_v2here?I would expect we could just implement the v2 callbacks for each of the transports, then just delete the originals and change the helper interface.
Maybe I'm not understanding the transition for 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.
@stevenportley This is Gemini response. I think she worded better than I did. lert me know if this makes sense. ```
"That is a very fair point, and in a single-repository project, changing the helper interface directly would indeed be the cleanest approach!
│
│ The reason we are introducing libhoth_send_request_v2 alongside the original is to prevent breaking compilation for external consumers (like
│ gbmc_havend in the BMC repo and hsm_usb_interface in the Haven HSM repo) which depend on libhoth but live in separate repositories.
│
│ If we changed the signature of the existing libhoth_send_request directly to return libhoth_error , it would immediately break those external
│ builds the next time they update their libhoth dependency.
│
│ By introducing the _v2 helpers, we allow those external teams to update libhoth safely, migrate their code to the V2 APIs at their own pace, and
│ once everyone is fully migrated, we will submit a cleanup PR to remove the legacy V1 helpers and rename these back to the clean interface."
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 think this implies that we :
If this were a heavily used API and the signature change was complicated, I would be tempted to go with this, but the signature change is just int -> uint64_t for the return type. This is only used in one or two places (from what I can tell), and most uses just compare the return type to LIBHOTH_OK.
Maybe try just making the signature change and seeing if it compiles okay with hothd before doing all of 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.
Awh thanks for clarifying the external user's use-cases. I think this would be an simplified approach that Ill look into.