connectionLost not invoked
Open
Nobody has claimed this yet.
bug
conch
new
priority-normal
soc2007
- Dominant language
- Python
- Stars
- 6k
- Forks
- 1.2k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 10
Description
 |
jrydberg reported |
|---|---|
| Trac ID | trac#2676 |
| Type | defect |
| Created | 2007-05-24 13:55:32Z |
The connectionLost method is not invoked for subsystem protocol instances
whenever the connection is lost for whatever reason.
Searchable metadata
trac-id__2676 2676
type__defect defect
reporter__jrydberg jrydberg
priority__normal normal
milestone__
branch__None None
branch_author__None None
status__new new
resolution__None None
component__conch conch
keywords__soc2007 soc2007
time__1180014932000000 1180014932000000
changetime__1552094592943393 1552094592943393
version__None None
owner__
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in the Conch subsystem protocol handling for connection loss and trace each path taken when a connection ends. Confirm that connectionLost is invoked for every loss reason, then add regression coverage demonstrating the callback is reached.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100