| Ticket UUID: | 581937ab1e2a1c69d61b23bd90179bd35f212d8d | ||
| Title: | async socket connect fail does not fire readable event | ||
| Type: | Bug | Created on: | 2014-03-24 12:26:30 |
| Submitter: | oehhar | Assigned to: | oehhar |
| Subsystem: | 27. Channel Types | Severity: | Severe |
| Priority: | 5 Medium | Last modified: | 2014-04-02 13:36:42 |
| Status: | Closed | Closed by: | oehhar |
| Resolution: | Fixed | Closed on: | 2014-04-02 13:36:42 |
| Version: | 8.5.15 | ||
| Description: | ||||
|
IssueOn windows, a readable fileevent on a failed async socket connect only fires, if there is also a writable fileevent.ExamplesFollowing examples are in wish so there is an event loop running.Only readable fileevent does not fire
% set h [socket -async localhost 30001]
sock448
% fileevent $h readable {puts R:[fconfigure $h -error];close $h}
Readable and writable fileevent fire bothFileevent fires, if there is also a writable file event ( as in bug [794839]):
% set h [socket -async localhost 30001]
sock448
% fileevent $h readable {puts R:[fconfigure $h -error];close $h}
% fileevent $h writable {puts W}
W
R:connection refused
TCL8.6.1The same issue is also present in tcl8.6.1, but already fixed in branch bug-13d3af3ad5, checkin [f1d2f6dbad]. | ||||
| User Comments: | ||||
oehhar added on 2014-04-02 12:47:26:
Fix and test in checkin [29adf4bac3] of branch bug-581937ab1e oehhar added on 2014-04-02 13:36:42:
Committed to core-8-5-branch by checkin [37dce67f70]. Bug closed. | ||||