-
Notifications
You must be signed in to change notification settings - Fork 596
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
refactor: use timeout type when possible #5572
Conversation
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.
lgtm, love the clean up! Left one question w.r.t ErrPacketTimeout
.
…bc-go into colin/3483-timeout-type-cleanup
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #5572 +/- ##
==========================================
- Coverage 81.20% 81.18% -0.03%
==========================================
Files 197 197
Lines 15268 15247 -21
==========================================
- Hits 12399 12378 -21
Misses 2404 2404
Partials 465 465
|
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.
nice cleanup! thanks @colin-axner
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.
Nice and clean! Thanks @colin-axner 🚀
Added backport label, I'm assuming we want it! |
* refactor: use timeout type when possible * review: consistent error type usage * nit: error wording --------- Co-authored-by: Damian Nolan <[email protected]> (cherry picked from commit de8eb6e)
* refactor: use timeout type when possible * review: consistent error type usage * nit: error wording --------- Co-authored-by: Damian Nolan <[email protected]> (cherry picked from commit de8eb6e) Co-authored-by: colin axnér <[email protected]>
Description
ref: #5404
Commit Message / Changelog Entry
see the guidelines for commit messages. (view raw markdown for examples)
Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.
docs/
) or specification (x/<module>/spec/
).godoc
comments.Files changed
in the Github PR explorer.Codecov Report
in the comment section below once CI passes.