feat: asynced both RPC operations (send_rpc/get_response) in RpcResult #18
Conversation
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
gbr1
approved these changes
Sep 29, 2025
mod: tcp_client and monitor use RpcResult async calls to get errors examples: Bridge test.ino with python code doc: impr Bridge call examples new API
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This should save the day
invoking Bridge.call() without .result returns a completely async result object
A situation like the following does not block the Monitor anymore
{ RpcResult res = Bridge.call("multiply", 1.0, 2.0); Monitor.println("TEST"); }