-
Notifications
You must be signed in to change notification settings - Fork 39
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
improve deadline error #2015
Merged
Merged
improve deadline error #2015
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
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 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 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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -34,13 +34,15 @@ const ( | |
ethCallAddrPadding = "000000000000000000000000" | ||
|
||
notAuthorised = "not authorised" | ||
serverBusy = "server busy. please retry later" | ||
|
||
longCacheTTL = 5 * time.Hour | ||
shortCacheTTL = 1 * time.Minute | ||
|
||
// hardcoding the maximum time for an RPC request | ||
// this value will be propagated to the node and enclave and all the operations | ||
maximumRPCCallDuration = 5 * time.Second | ||
maximumRPCCallDuration = 5 * time.Second | ||
sendTransactionDuration = 20 * time.Second | ||
) | ||
|
||
var rpcNotImplemented = fmt.Errorf("rpc endpoint not implemented") | ||
|
@@ -52,6 +54,7 @@ type ExecCfg struct { | |
tryUntilAuthorised bool | ||
adjustArgs func(acct *GWAccount) []any | ||
cacheCfg *CacheCfg | ||
deadline time.Duration | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Nitpick I'd probably call it timeout rather than deadline |
||
} | ||
|
||
type CacheStrategy uint8 | ||
|
@@ -136,10 +139,19 @@ func ExecAuthRPC[R any](ctx context.Context, w *Services, cfg *ExecCfg, method s | |
} | ||
|
||
// wrap the context with a timeout to prevent long executions | ||
timeoutContext, cancelCtx := context.WithTimeout(ctx, maximumRPCCallDuration) | ||
deadline := cfg.deadline | ||
// if not set, use default | ||
if deadline == 0 { | ||
deadline = maximumRPCCallDuration | ||
} | ||
timeoutContext, cancelCtx := context.WithTimeout(ctx, deadline) | ||
defer cancelCtx() | ||
|
||
err := rpcClient.CallContext(timeoutContext, &result, method, adjustedArgs...) | ||
// return a friendly error to the user | ||
if err != nil && errors.Is(err, context.DeadlineExceeded) { | ||
return nil, fmt.Errorf(serverBusy) | ||
} | ||
return result, err | ||
}) | ||
if err != nil { | ||
|
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.
should it say retry? i.e. the transaction might have actually gone through, so you wouldn't want to send again, just go into reconcilliation
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.
the error response is generic for all rpc calls. The tx submission has a much higher timeout, so it shouldn't really be shown there, unless there is something really wrong