Merge ~ines-almeida/txpkgupload:update-txpkgupload-dtpport-selection into txpkgupload:master
Proposed by
Ines Almeida
Status: | Merged |
---|---|
Approved by: | Ines Almeida |
Approved revision: | 69c165feb25cc5927ed45704828cd3f118e9dc77 |
Merge reported by: | Otto Co-Pilot |
Merged at revision: | not available |
Proposed branch: | ~ines-almeida/txpkgupload:update-txpkgupload-dtpport-selection |
Merge into: | txpkgupload:master |
Diff against target: |
43 lines (+15/-0) 1 file modified
src/txpkgupload/twistedftp.py (+15/-0) |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Colin Watson | Approve | ||
Review via email:
|
Commit message
Add portsInUse set in txpkgupload code so that passive FTP doesn't reuse connected ports
Description of the change
Currently some dput uploads are failing in production. We suspect that txpkgupload is not selecting the right ports for users to use.
Possible considerations:
- Would it be possible for a port to not be cleaned up after closing, hence limiting the port space we currently have?
To post a comment you must log in.
There's definitely a non-zero risk of something like that, but I don't know how to assess how likely it is, and this seems worth a try. I guess we can at least check logs occasionally to see whether the data ports we're issuing seem to be growing without bound?