twisted / twisted/twisted

no way for ftp data protocols to fail

Open
#4,359 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement ftp new priority-normal
Dominant language
Python
Stars
6k
Forks
1.2k
Avg merge
2d 10h
Merged PRs (30d)
10

Description

jrydberg's avatar jrydberg reported
Trac ID trac#4359
Type enhancement
Created 2010-03-08 10:39:33Z

There is currently no way to signal from a FTP data protocol (like FTPFileListProtocol) if there's an errorin the data received.

The deferred for the protocol wrapper is called when the connection is closed (or lost). There should be a way to manually signal that processing has finished (or failed).

Searchable metadata
trac-id__4359 4359
type__enhancement enhancement
reporter__jrydberg jrydberg
priority__normal normal
milestone__ 
branch__ 
branch_author__ 
status__new new
resolution__None None
component__ftp ftp
keywords__ 
time__1268044773000000 1268044773000000
changetime__1268045223000000 1268045223000000
version__None None
owner__ 
cc__spiv

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by inspecting FTP data protocols, including FTPFileListProtocol, and trace how the protocol wrapper invokes its deferred when the connection closes or is lost. Determine where processing completion and failure can be signaled, then add coverage showing both outcomes for received data.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
networking
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.