https://redmine.ruby-lang.org/https://redmine.ruby-lang.org/favicon.ico?17113305112013-05-07T16:45:44ZRuby Issue Tracking SystemRuby master - Bug #8374: race condition when two threads require a gemhttps://redmine.ruby-lang.org/issues/8374?journal_id=391752013-05-07T16:45:44Znobu (Nobuyoshi Nakada)nobu@ruby-lang.org
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/39175/diff?detail_id=28296">diff</a>)</li><li><strong>Category</strong> set to <i>lib</i></li><li><strong>Status</strong> changed from <i>Open</i> to <i>Assigned</i></li><li><strong>Assignee</strong> set to <i>drbrain (Eric Hodel)</i></li></ul><p>Seems rubygems specific.</p> Ruby master - Bug #8374: race condition when two threads require a gemhttps://redmine.ruby-lang.org/issues/8374?journal_id=402832013-07-04T08:06:12Zdrbrain (Eric Hodel)drbrain@segment7.net
<ul><li><strong>Subject</strong> changed from <i>race condition when two threads require a gem with a C extension</i> to <i>race condition when two threads require a gem</i></li></ul><p>This is reproducible without a C extension, updated subject.</p> Ruby master - Bug #8374: race condition when two threads require a gemhttps://redmine.ruby-lang.org/issues/8374?journal_id=403662013-07-09T07:10:04Zdrbrain (Eric Hodel)drbrain@segment7.net
<ul><li><strong>Status</strong> changed from <i>Assigned</i> to <i>Closed</i></li></ul><p>This has been fixed in rubygems master and 2.0 branches.</p>