Repository navigation
Conversation
This was referenced Oct 23, 2026
moetemp
force-pushed
the
moe/up/resource-method-record-result
branch
from
October 23, 2026 04:35
095326a to
e3a5c38
Compare
Contributor
Author
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What changed?
This PR binds a resource method to an operation that returns a WIT record.
The fix is in the second commit, e3a5c387. The first commit adds
get-profiletouser-servicewith the output on main.Why?
The result check knew only resource and proto results, so the method became a stub that raises.
How did you test it?
The goldens show the bound call in place of the stub. The Python sample test calls
user.get_profile().