-
Notifications
You must be signed in to change notification settings - Fork 102
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
feat(routing/http/server): add routing timeout #720
Conversation
Codecov ReportAttention: Patch coverage is
@@ Coverage Diff @@
## main #720 +/- ##
==========================================
+ Coverage 60.34% 60.35% +0.01%
==========================================
Files 243 243
Lines 31039 31056 +17
==========================================
+ Hits 18730 18745 +15
- Misses 10644 10645 +1
- Partials 1665 1666 +1
... and 5 files with indirect coverage changes 🚨 Try these New Features:
|
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.
Tested in ipfs/someguy#87, lgtm, thank you!
…request timeouts (#87) * fix: larger duration buckets for better visibility * feat: log accept header * fix: move instrumentation to boxo * feat: add tracing with auth token * feat: add 30 second request timeout * chore: remove replace directive * chore: add missing funcSampler * chore: remove request timeout this isn't working too well. We need to look more deeply into this * chore: update changelog * chore: go mod tidy * chore: go-libp2p-kad-dht v0.28.1 * chore: latest boxo#720 * chore: mod tidy * chore: boxo main with ipfs/boxo#720 and ipfs/boxo#718 * Apply suggestions from code review Co-authored-by: Marcin Rataj <lidel@lidel.org> * fix: typo --------- Co-authored-by: Daniel N <2color@users.noreply.github.com> Co-authored-by: Marcin Rataj <lidel@lidel.org>
Why
See ipfs/someguy#88.
TL;DR: Without any routing timeout, routing requests will run indefinitely if the record limit isn't reached.