{"action":"created","issue":{"url":"https://api.github.com/repos/cf-tm-bot/capi/issues/320","repository_url":"https://api.github.com/repos/cf-tm-bot/capi","labels_url":"https://api.github.com/repos/cf-tm-bot/capi/issues/320/labels{/name}","comments_url":"https://api.github.com/repos/cf-tm-bot/capi/issues/320/comments","events_url":"https://api.github.com/repos/cf-tm-bot/capi/issues/320/events","html_url":"https://github.com/cf-tm-bot/capi/issues/320","id":186354676,"number":320,"title":"Resolve pipeline failures due to segfaults in UAA libraries inside of cloud_controller_ng - Story Id: 133266195","user":{"login":"cf-tm-bot","id":20690070,"avatar_url":"https://avatars.githubusercontent.com/u/20690070?v=3","gravatar_id":"","url":"https://api.github.com/users/cf-tm-bot","html_url":"https://github.com/cf-tm-bot","followers_url":"https://api.github.com/users/cf-tm-bot/followers","following_url":"https://api.github.com/users/cf-tm-bot/following{/other_user}","gists_url":"https://api.github.com/users/cf-tm-bot/gists{/gist_id}","starred_url":"https://api.github.com/users/cf-tm-bot/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/cf-tm-bot/subscriptions","organizations_url":"https://api.github.com/users/cf-tm-bot/orgs","repos_url":"https://api.github.com/users/cf-tm-bot/repos","events_url":"https://api.github.com/users/cf-tm-bot/events{/privacy}","received_events_url":"https://api.github.com/users/cf-tm-bot/received_events","type":"User","site_admin":false},"labels":[{"id":447324187,"url":"https://api.github.com/repos/cf-tm-bot/capi/labels/bug","name":"bug","color":"ee0701","default":true},{"id":447329564,"url":"https://api.github.com/repos/cf-tm-bot/capi/labels/started","name":"started","color":"c8cbd0","default":false}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":11,"created_at":"2016-10-31T18:04:04Z","updated_at":"2016-10-31T18:05:00Z","closed_at":null,"body":"\n\n---\n\nMirrors: [story 133266195](https://www.pivotaltracker.com/story/show/133266195) submitted on Oct 27, 2016 UTC\n- **Requester**: Aakash Shah\n- **Owners**: Timothy Hausler, Jonathan Berkhahn\n- **Estimate**: 0.0"},"comment":{"url":"https://api.github.com/repos/cf-tm-bot/capi/issues/comments/257371903","html_url":"https://github.com/cf-tm-bot/capi/issues/320#issuecomment-257371903","issue_url":"https://api.github.com/repos/cf-tm-bot/capi/issues/320","id":257371903,"user":{"login":"cf-tm-bot","id":20690070,"avatar_url":"https://avatars.githubusercontent.com/u/20690070?v=3","gravatar_id":"","url":"https://api.github.com/users/cf-tm-bot","html_url":"https://github.com/cf-tm-bot","followers_url":"https://api.github.com/users/cf-tm-bot/followers","following_url":"https://api.github.com/users/cf-tm-bot/following{/other_user}","gists_url":"https://api.github.com/users/cf-tm-bot/gists{/gist_id}","starred_url":"https://api.github.com/users/cf-tm-bot/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/cf-tm-bot/subscriptions","organizations_url":"https://api.github.com/users/cf-tm-bot/orgs","repos_url":"https://api.github.com/users/cf-tm-bot/repos","events_url":"https://api.github.com/users/cf-tm-bot/events{/privacy}","received_events_url":"https://api.github.com/users/cf-tm-bot/received_events","type":"User","site_admin":false},"created_at":"2016-10-31T18:05:00Z","updated_at":"2016-10-31T18:05:00Z","body":"*Anonymous* [commented](https://www.pivotaltracker.com/n/projects/966314/stories/133266195/comments/153999359) on Oct 28, 2016, 3.10 PM UTC:\n\nIt looks like the fix for [12292](https://bugs.ruby-lang.org/issues/12292) was backported to ruby's 2.3 branch [on August 11](https://github.com/ruby/ruby/commit/88d76cfdcd19bab721bfefadaa4f1c0de4e3c0ff)  but it is [not in the 2.3.1 branch](https://github.com/ruby/ruby/compare/v2_3_1...ruby_2_3).  Incidentally, CAPI's ruby 2.3 blob [hasn't been updated since April 27](https://github.com/cloudfoundry/capi-release/blame/652a83f18c797908791d6c5adb508fd0f39dce10/config/blobs.yml) so it seems unlikely (impossible?) to have this fix.  Maybe Xena just hasn't come across it because they are running CATs with fewer nodes, and thus are less vulnerable to concurrency issues.\n\n<!--\nComment Id: 153999359\n-->"}}
{"actor":{"display_login":"cf-tm-bot"}}