|
2014-05-20
| ||
| 15:06 | • Closed ticket [13d3af3ad5]: IPV6 only used for IPV4/IPV6 sockets on windows plus 7 other changes artifact: 201dc14fca user: oehhar | |
|
2014-04-04
| ||
| 11:53 | Add tests for bugs [336441ed59] and [581937ab1e] from core-8-5-branch. check-in: b602826a44 user: max tags: bug-13d3af3ad5 | |
|
2014-04-02
| ||
| 13:36 | • Closed ticket [581937ab1e]: async socket connect fail does not fire readable event plus 7 other changes artifact: 5dd96060c5 user: oehhar | |
| 13:33 | Fix bug [581937ab1e]: fire readable event on async socket connect failure check-in: 37dce67f70 user: oehhar tags: core-8-5-branch | |
| 12:47 | • Ticket [581937ab1e] async socket connect fail does not fire readable event status still Open with 5 other changes artifact: 0d9b2bc904 user: oehhar | |
| 12:43 | Fix bug [581937ab1e]: fire readable event on async socket connect failure Closed-Leaf check-in: 29adf4bac3 user: oehhar tags: bug-581937ab1e | |
|
2014-03-24
| ||
| 12:30 | • Ticket [581937ab1e] async socket connect fail does not fire readable event status still Open with 3 other changes artifact: 91f3b8db51 user: oehhar | |
| 12:26 | • New ticket [581937ab1e]. artifact: c149625776 user: oehhar | |
| Ticket UUID: | 581937ab1e2a1c69d61b23bd90179bd35f212d8d | |||
| Title: | async socket connect fail does not fire readable event | |||
| Type: | Bug | Version: | 8.5.15 | |
| Submitter: | oehhar | Created on: | 2014-03-24 12:26:30 | |
| Subsystem: | 27. Channel Types | Assigned To: | oehhar | |
| Priority: | 5 Medium | Severity: | Severe | |
| Status: | Closed | Last Modified: | 2014-04-02 13:36:42 | |
| Resolution: | Fixed | Closed By: | oehhar | |
| Closed on: | 2014-04-02 13:36:42 | |||
| 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 13:36:42:
Committed to core-8-5-branch by checkin [37dce67f70]. Bug closed. oehhar added on 2014-04-02 12:47:26: Fix and test in checkin [29adf4bac3] of branch bug-581937ab1e | |||