{"action":"closed","issue":{"url":"https://api.github.com/repos/yarnpkg/yarn/issues/948","repository_url":"https://api.github.com/repos/yarnpkg/yarn","labels_url":"https://api.github.com/repos/yarnpkg/yarn/issues/948/labels{/name}","comments_url":"https://api.github.com/repos/yarnpkg/yarn/issues/948/comments","events_url":"https://api.github.com/repos/yarnpkg/yarn/issues/948/events","html_url":"https://github.com/yarnpkg/yarn/issues/948","id":182659404,"number":948,"title":"Stack traces shouldn't leak into the output","user":{"login":"wycats","id":4,"avatar_url":"https://avatars.githubusercontent.com/u/4?v=3","gravatar_id":"","url":"https://api.github.com/users/wycats","html_url":"https://github.com/wycats","followers_url":"https://api.github.com/users/wycats/followers","following_url":"https://api.github.com/users/wycats/following{/other_user}","gists_url":"https://api.github.com/users/wycats/gists{/gist_id}","starred_url":"https://api.github.com/users/wycats/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/wycats/subscriptions","organizations_url":"https://api.github.com/users/wycats/orgs","repos_url":"https://api.github.com/users/wycats/repos","events_url":"https://api.github.com/users/wycats/events{/privacy}","received_events_url":"https://api.github.com/users/wycats/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/yarnpkg/yarn/labels/discussion","name":"discussion","color":"c2e0c6"},{"url":"https://api.github.com/repos/yarnpkg/yarn/labels/enhancement","name":"enhancement","color":"006b75"}],"state":"closed","locked":false,"assignee":{"login":"kittens","id":853712,"avatar_url":"https://avatars.githubusercontent.com/u/853712?v=3","gravatar_id":"","url":"https://api.github.com/users/kittens","html_url":"https://github.com/kittens","followers_url":"https://api.github.com/users/kittens/followers","following_url":"https://api.github.com/users/kittens/following{/other_user}","gists_url":"https://api.github.com/users/kittens/gists{/gist_id}","starred_url":"https://api.github.com/users/kittens/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kittens/subscriptions","organizations_url":"https://api.github.com/users/kittens/orgs","repos_url":"https://api.github.com/users/kittens/repos","events_url":"https://api.github.com/users/kittens/events{/privacy}","received_events_url":"https://api.github.com/users/kittens/received_events","type":"User","site_admin":false},"assignees":[{"login":"kittens","id":853712,"avatar_url":"https://avatars.githubusercontent.com/u/853712?v=3","gravatar_id":"","url":"https://api.github.com/users/kittens","html_url":"https://github.com/kittens","followers_url":"https://api.github.com/users/kittens/followers","following_url":"https://api.github.com/users/kittens/following{/other_user}","gists_url":"https://api.github.com/users/kittens/gists{/gist_id}","starred_url":"https://api.github.com/users/kittens/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kittens/subscriptions","organizations_url":"https://api.github.com/users/kittens/orgs","repos_url":"https://api.github.com/users/kittens/repos","events_url":"https://api.github.com/users/kittens/events{/privacy}","received_events_url":"https://api.github.com/users/kittens/received_events","type":"User","site_admin":false}],"milestone":null,"comments":1,"created_at":"2016-10-12T23:30:02Z","updated_at":"2016-10-15T14:39:17Z","closed_at":"2016-10-15T14:39:17Z","body":"In general, we should always be able to convert JS exceptions into contextual, human-readable error messages. Unfortunately, errors sometimes make it through to the top of the process because we haven't properly handled the error yet. (#943, #944, #928, #921, #919, etc. etc.)\r\n\r\nIn my opinion, we should have a zero-tolerance policy for stack traces that are reported in raw form to users.\r\n\r\nProposal: If a stack trace makes it to the top of the process, we should capture it, save it off in a long file, and give the user a red error indicating that an unexpected problem occurred, and giving them a command to run to show the original error.\r\n\r\nA nice side-effect of doing this is that we can also put other contextual information in the log file and give users a really nice single file to include with bug reports."}}
{"actor":{"display_login":"kittens"}}