-
Notifications
You must be signed in to change notification settings - Fork 139
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
Handle jd-client
config error
#987
Handle jd-client
config error
#987
Conversation
Bencher
Click to view all benchmark results
Bencher - Continuous Benchmarking View Public Perf Page Docs | Repo | Chat | Help |
Bencher
Click to view all benchmark results
Bencher - Continuous Benchmarking View Public Perf Page Docs | Repo | Chat | Help |
Bencher
🚨 1 ALERT: Threshold Boundary Limit exceeded!
Click to view all benchmark results
Bencher - Continuous Benchmarking View Public Perf Page Docs | Repo | Chat | Help |
Bencher
🚨 23 ALERTS: Threshold Boundary Limits exceeded!
Click to view all benchmark results
Bencher - Continuous Benchmarking View Public Perf Page Docs | Repo | Chat | Help |
thanks @jbesraa we have a WIP refactor PR that touches this part of the code #937 @rrybarczyk is working on some adjustments via plebhash#61 I suggest we revert #987 to draft and wait until #937 is merged |
Hm, While #937 looks promising I would not block this PR. #937 will take much longer to be reviewed and approved. This PR would be very beneficial in terms of error handling and can be a quick win. |
ok sounds good, I'll rebase #937 after we merge this, and I can coordinate with @rrybarczyk so she plebhash#61 follows along |
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.
ACK
match SetupConnectionHandler::setup(&mut receiver, &mut sender, proxy_address).await { | ||
Ok(_) => {} | ||
Err(e) => { | ||
error!("Error setting up connection: {:?}", e); | ||
return Err(Error::ConnectionSetup); | ||
} | ||
}; |
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.
Since the Ok
case doesn't do anything, using if let
is cleaner and makes the code easier to read.
match SetupConnectionHandler::setup(&mut receiver, &mut sender, proxy_address).await { | |
Ok(_) => {} | |
Err(e) => { | |
error!("Error setting up connection: {:?}", e); | |
return Err(Error::ConnectionSetup); | |
} | |
}; | |
if let Err(e) = SetupConnectionHandler::setup(&mut receiver, &mut sender, proxy_address).await { | |
error!("Error setting up connection: {:?}", e); | |
return Err(Error::ConnectionSetup); | |
} |
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.
Ah, good point. I left the match
as is and moved the success
log into the ok
arm. thank you
7d99668
to
8fd1876
Compare
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.
ACK bcbf6a0
I think all config/args in the roles should be refactored as there is a lot of duplicate logic/logic that is in the wrong place. I did not end up including this refactor in the review for @plebhash's #813 PR because it started to feel out of scope. I think an immediate fix to make sure the JD config is properly configured is fine if we are time-pressed on this, but if it is not pressing, let's address all of this logic in a single issue/PR. It will fall into the "roles refactor" category. See #997. |
@rrybarczyk I dont think its time pressed, it is part of the |
as discussed on the call, let's avoid fixing the let's keep PRs as atomic as possible so coordination with #813 is easier |
8fd1876
to
9cfaebd
Compare
Deleted unrelated commit |
resolves #863