twistd sometimes errors with "reactor already installed"
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 6k
- Forks
- 1.2k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 10
Description
| ivank reported | |
|---|---|
| Trac ID | trac#3785 |
| Type | defect |
| Created | 2009-04-17 16:30:05Z |
When using twistd -r , and dropin.cache is not generated yet, and imports the reactor (or imports anything that imports the reactor), twistd fails with:
"/usr/local/bin/twistd: The specified reactor cannot be used, failed with error: reactor already installed."
This only happens if the reactor is imported when the plugin file is loaded (imported?). It does not happen if the reactor is imported in makeService.
I don't believe this is documented anywhere, the error is uninformative, and the failure is hard to track down.
Searchable metadata
trac-id__3785 3785
type__defect defect
reporter__ivank ivank
priority__normal normal
milestone__
branch__
branch_author__
status__new new
resolution__None None
component__core core
keywords__documentation_twistd documentation twistd
time__1239985805000000 1239985805000000
changetime__1279126898000000 1279126898000000
version__None None
owner__ivank ivank
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 at the twistd entry point and trace reactor selection, plugin loading, and the makeService path. Reproduce the failure with a non-select reactor, an ungenerated dropin.cache, and a plugin that imports the reactor, then compare it with importing the reactor in makeService. Done means the reported startup failure is addressed or made informative, with the behavior documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100