Bug #21
should terminate @receiver_thread of Net::IMAP safely
| Status: | Closed | Start date: | 05/29/2008 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | % Done: | 100% |
||
| Category: | lib | |||
| Target version: | 1.9.2 | |||
| ruby -v: | - |
Description
@receiver_thread of Net::IMAP may be terminated by exception, and this causes the process termination if Thread.abort_on_exception is true. Then Net::IMAP#disconnect does not call @receiver_thread.join if TCPSocket#close raises an exception. Reported by Tanaka Akira in [ruby-dev:34821].
Associated revisions
* lib/net/imap.rb (disconnect): terminates @receiver_thread even if
@sock.shutdown raises an exception. [ruby-dev:34881]
History
Updated by yugui (Yuki Sonoda) over 3 years ago
- Target version set to 2.0.0
Updated by mame (Yusuke Endoh) about 2 years ago
- Category set to lib
- Target version changed from 2.0.0 to 1.9.2
- ruby -v set to -
Hi, Shugo Is this issue still unsolved? -- Yusuke Endoh <mame@tsg.ne.jp>
Updated by shugo (Shugo Maeda) about 2 years ago
- Status changed from Assigned to Closed
- % Done changed from 0 to 100
This issue was solved with changeset r27690. Shugo, thank you for reporting this issue. Your contribution to Ruby is greatly appreciated. May Ruby be with you.