-
Notifications
You must be signed in to change notification settings - Fork 44
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
Overhaul core Tracker: review whitelist functionality #1269
Overhaul core Tracker: review whitelist functionality #1269
Conversation
Following HTTP structure.
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## develop #1269 +/- ##
===========================================
+ Coverage 80.97% 81.23% +0.25%
===========================================
Files 207 212 +5
Lines 14762 14891 +129
Branches 14762 14891 +129
===========================================
+ Hits 11954 12096 +142
+ Misses 2610 2604 -6
+ Partials 198 191 -7 ☔ View full report in Codecov by Sentry. |
95eb3f7
to
dec742e
Compare
e01282b
to
e48aaf5
Compare
168b5b6
to
dea33ed
Compare
dea33ed
to
74815ab
Compare
281857a
to
37a142e
Compare
…racker_core package
I cant' move the authentication functionality to the |
…cker_core package
ACK eca5c59 |
Overhaul core Tracker: review whitelist functionality.
Sub-tasks
servers::udp::handlers::{announce, scrape}
.udp-tracker-core
later.services::announce::invoke()
in the HTTP tracker to thehttp-tracker-core
package.services::announce::invoke()
in the UDP tracker to theudp-tracker-core
package.http-tracker-core
package.announce
requestscrape
requestudp-tracker-core
package.announce
requestscrape
requestAdd version module also for the UDP tracker. I don't see any reason to useI will leave this until we introduce a new major version.v1
in the http tracker but not in the UDP tracker.Sub-tasks for a new PR
I've left these tasks for a new issue. This PR is just moving things and the new tasks imply changing function signatures.
Result<AnnounceData, AnnounceError>
when the torrent is not included in the whitelist.Result<ScrapeData, ScrapeError>
so we are able to return errors in the future without breaking the public API.