SFTP: use new eventual utilities from deferredutil #1877

Closed
opened 2012-11-24 19:41:05 +00:00 by davidsarah · 4 comments
davidsarah commented 2012-11-24 19:41:05 +00:00
Owner

The cloud backend + leasedb merge adds several deferred utilities: https://github.com/davidsarah/tahoe-lafs/commit/7671b3e33f0c91e764fb869175ff.

eventually_callback and eventually_errback were modelled on the versions already in sftpd.py, with an error-reporting improvement. eventual_chain is an abstraction of the pattern

source.addCallbacks(eventually_callback(target), eventually_errback(target))

which is used twice in sftpd.py. So we should change sftpd to use these versions, once the cloud backend + leasedb merge has landed.

The cloud backend + leasedb merge adds several deferred utilities: <https://github.com/davidsarah/tahoe-lafs/commit/7671b3e33f0c91e764fb869175ff>. `eventually_callback` and `eventually_errback` were modelled on the versions already in sftpd.py, with an error-reporting improvement. `eventual_chain` is an abstraction of the pattern ``` source.addCallbacks(eventually_callback(target), eventually_errback(target)) ``` which is used twice in sftpd.py. So we should change sftpd to use these versions, once the cloud backend + leasedb merge has landed.
tahoe-lafs added the
code-frontend
minor
defect
1.9.2
labels 2012-11-24 19:41:05 +00:00
tahoe-lafs added this to the 1.11.0 milestone 2012-11-24 19:41:05 +00:00
tahoe-lafs modified the milestone from 1.11.0 to 1.12.0 2013-08-06 23:04:22 +00:00
warner added
code-frontend-ftp-sftp
and removed
code-frontend
labels 2014-12-02 19:52:57 +00:00

Milestone renamed

Milestone renamed
warner modified the milestone from 1.12.0 to 1.13.0 2016-03-22 05:02:25 +00:00

renaming milestone

renaming milestone
warner modified the milestone from 1.13.0 to 1.14.0 2016-06-28 18:17:14 +00:00

Moving tickets out of closed milestones.

Moving tickets out of closed milestones.
exarkun modified the milestone from 1.14.0 to 1.15.0 2020-06-30 14:45:46 +00:00

The established line of development on the "cloud backend" branch has been abandoned. This ticket is being closed as part of a batch-ticket cleanup for "cloud backend"-related tickets.

If this is a bug, it is probably genuinely no longer relevant. The "cloud backend" branch is too large and unwieldy to ever be merged into the main line of development (particularly now that the Python 3 porting effort is significantly underway).

If this is a feature, it may be relevant to some future efforts - if they are sufficiently similar to the "cloud backend" effort - but I am still closing it because there are no immediate plans for a new development effort in such a direction.

Tickets related to the "leasedb" are included in this set because the "leasedb" code is in the "cloud backend" branch and fairly well intertwined with the "cloud backend". If there is interest in lease implementation change at some future time then that effort will essentially have to be restarted as well.

The established line of development on the "cloud backend" branch has been abandoned. This ticket is being closed as part of a batch-ticket cleanup for "cloud backend"-related tickets. If this is a bug, it is probably genuinely no longer relevant. The "cloud backend" branch is too large and unwieldy to ever be merged into the main line of development (particularly now that the Python 3 porting effort is significantly underway). If this is a feature, it may be relevant to some future efforts - if they are sufficiently similar to the "cloud backend" effort - but I am still closing it because there are no immediate plans for a new development effort in such a direction. Tickets related to the "leasedb" are included in this set because the "leasedb" code is in the "cloud backend" branch and fairly well intertwined with the "cloud backend". If there is interest in lease implementation change at some future time then that effort will essentially have to be restarted as well.
exarkun added the
wontfix
label 2020-10-30 12:35:44 +00:00
Sign in to join this conversation.
No Milestone
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Reference: tahoe-lafs/trac-2024-07-25#1877
No description provided.