Glib2 and Gtk2 reactor don't always report writeable events on Windows
Open
Nobody has claimed this yet.
bug
core
gtk
new
priority-normal
windows
- Dominant language
- Python
- Stars
- 6k
- Forks
- 1.2k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 10
Description
 |
@exarkun reported |
|---|---|
| Trac ID | trac#4744 |
| Type | defect |
| Created | 2010-11-23 02:51:30Z |
twisted.internet.test.test_tcp.TCPClientTestsBuilder.test_disconnectWhileProducing fails on Windows for these two reactors, apparently because while we are asking the g* io system to tell us about writeability, it never does.
This seems like it's probably a bug in glib or gobject or gtk or pygobject or pygtk.
Searchable metadata
trac-id__4744 4744
type__defect defect
reporter__exarkun exarkun
priority__normal normal
milestone__
branch__
branch_author__
status__new new
resolution__None None
component__core core
keywords__windows__gtk windows, gtk
time__1290480690000000 1290480690000000
changetime__1389785803000000 1389785803000000
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 with twisted.internet.test.test_tcp.TCPClientTestsBuilder.test_disconnectWhileProducing and compare the Glib2 and Gtk2 reactors on Windows. Determine why requested writeability notifications are not delivered, then confirm the test passes for both reactors on Windows.
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
- Needs clarification
- Newbie friendliness
- 25/100