Avoid pending Twisted deprecations #490
No reviewers
Labels
No Label
Benchmarking and Performance
HTTP Storage Protocol
Nevow Removal
Python 3 Porting
not-for-merge
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: tahoe-lafs/tahoe-lafs#490
Loading…
Reference in New Issue
No description provided.
Delete Branch "pending-deprecations"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Replaces getClientIP with getClientAddress if possible. Fixes the deprecation builder.
This introduces "uncovered" code because coverage is only measured when running the test suite against the released version of Twisted, not trunk@HEAD, and one of the codepaths is currently only exercised against Twisted trunk@HEAD. This seems not ideal but not catastrophic to me since we are actually testing both code paths - we just don't measure one of them automatically.
When the next Twisted release happens, the situation will get a bit worse because we will only test the newer codepath - because both the Twisted-release and Twisted-trunk@HEAD builds will both be running the newer codepath. To keep testing the older codepath, we would need a CI job that uses other than the newest allowed released Twisted. Not sure what to do about that (apart from the semi-obvious: set up a new CI job).
Codecov Report
85.6% <63.63%> (-2.23%)
92.82% <0%> (-2.47%)
95.65% <0%> (-1.02%)
93.38% <0%> (-0.81%)
95.53% <0%> (+0.27%)
Continue to review full report at Codecov.