{"action":"created","issue":{"url":"https://api.github.com/repos/rubinius/rubinius/issues/3663","repository_url":"https://api.github.com/repos/rubinius/rubinius","labels_url":"https://api.github.com/repos/rubinius/rubinius/issues/3663/labels{/name}","comments_url":"https://api.github.com/repos/rubinius/rubinius/issues/3663/comments","events_url":"https://api.github.com/repos/rubinius/rubinius/issues/3663/events","html_url":"https://github.com/rubinius/rubinius/issues/3663","id":158556796,"number":3663,"title":"Issue installing guard and running specs","user":{"login":"brixen","id":85,"avatar_url":"https://avatars.githubusercontent.com/u/85?v=3","gravatar_id":"","url":"https://api.github.com/users/brixen","html_url":"https://github.com/brixen","followers_url":"https://api.github.com/users/brixen/followers","following_url":"https://api.github.com/users/brixen/following{/other_user}","gists_url":"https://api.github.com/users/brixen/gists{/gist_id}","starred_url":"https://api.github.com/users/brixen/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/brixen/subscriptions","organizations_url":"https://api.github.com/users/brixen/orgs","repos_url":"https://api.github.com/users/brixen/repos","events_url":"https://api.github.com/users/brixen/events{/privacy}","received_events_url":"https://api.github.com/users/brixen/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2016-06-05T14:25:39Z","updated_at":"2016-06-05T19:11:06Z","closed_at":null,"body":"Tracking this issue here https://github.com/guard/listen/issues/400"},"comment":{"url":"https://api.github.com/repos/rubinius/rubinius/issues/comments/223831239","html_url":"https://github.com/rubinius/rubinius/issues/3663#issuecomment-223831239","issue_url":"https://api.github.com/repos/rubinius/rubinius/issues/3663","id":223831239,"user":{"login":"brixen","id":85,"avatar_url":"https://avatars.githubusercontent.com/u/85?v=3","gravatar_id":"","url":"https://api.github.com/users/brixen","html_url":"https://github.com/brixen","followers_url":"https://api.github.com/users/brixen/followers","following_url":"https://api.github.com/users/brixen/following{/other_user}","gists_url":"https://api.github.com/users/brixen/gists{/gist_id}","starred_url":"https://api.github.com/users/brixen/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/brixen/subscriptions","organizations_url":"https://api.github.com/users/brixen/orgs","repos_url":"https://api.github.com/users/brixen/repos","events_url":"https://api.github.com/users/brixen/events{/privacy}","received_events_url":"https://api.github.com/users/brixen/received_events","type":"User","site_admin":false},"created_at":"2016-06-05T19:11:06Z","updated_at":"2016-06-05T19:11:06Z","body":"@thedrow we do not generally match MRI's verbiage for many reasons, but mostly because they are \"non-executable\" content and code should not be matching on arbitrary Strings when there are proper instances of classes (eg an RuntimeError, ArgumentError, etc). Something that exacerbates the problem you're seeing is MRI's very poor use of attributes on Exception classes to provide actual information in a way that can be computed (ie code can make proper OO method calls instead of random regexp matching Strings).\r\n\r\nI have no intention of matching MRI Strings but I'm happy to support better OO APIs on Exception classes or elsewhere to support better code."}}
{"actor":{"display_login":"brixen"}}