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

Type sync network context send errors #5808

Merged
merged 2 commits into from
May 17, 2024

Conversation

dapplion
Copy link
Collaborator

Issue Addressed

SyncNetworkContext has a bunch of functions that send messages to network channel and processor channel with signature

) -> Result<LookupRequestResult, &'static str> {

So far this is okay-ish, but in das we introduce more complex failure modes that can't be coerced to a static string. See:

Err(_) => Err("custody_send_error"),

Proposed Changes

Type sync network context send errors in unstable, and backport to das when merged

@@ -52,31 +52,43 @@ pub enum RpcEvent<T> {
RPCError(RPCError),
}

pub type RpcProcessingResult<T> = Result<(T, Duration), LookupFailure>;
pub type RpcRequestResult<T> = Result<(T, Duration), RpcResponseError>;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

RpcResponseResult

@jimmygchen
Copy link
Member

@mergify queue

Copy link

mergify bot commented May 17, 2024

queue

✅ The pull request has been merged automatically

The pull request has been merged automatically at 8006418

@jimmygchen jimmygchen added the ready-for-merge This PR is ready to merge. label May 17, 2024
mergify bot added a commit that referenced this pull request May 17, 2024
@mergify mergify bot merged commit 8006418 into sigp:unstable May 17, 2024
27 of 28 checks passed
@dapplion dapplion deleted the type-sync-network-send-errors branch May 20, 2024 15:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ready-for-merge This PR is ready to merge.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants