{"action":"opened","issue":{"url":"https://api.github.com/repos/zopefoundation/zope.component/issues/11","labels_url":"https://api.github.com/repos/zopefoundation/zope.component/issues/11/labels{/name}","comments_url":"https://api.github.com/repos/zopefoundation/zope.component/issues/11/comments","events_url":"https://api.github.com/repos/zopefoundation/zope.component/issues/11/events","html_url":"https://github.com/zopefoundation/zope.component/issues/11","id":55530405,"number":11,"title":"Could not adapt error silently swallows exceptions in adaption","user":{"login":"tseaver","id":242750,"avatar_url":"https://avatars.githubusercontent.com/u/242750?v=3","gravatar_id":"","url":"https://api.github.com/users/tseaver","html_url":"https://github.com/tseaver","followers_url":"https://api.github.com/users/tseaver/followers","following_url":"https://api.github.com/users/tseaver/following{/other_user}","gists_url":"https://api.github.com/users/tseaver/gists{/gist_id}","starred_url":"https://api.github.com/users/tseaver/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/tseaver/subscriptions","organizations_url":"https://api.github.com/users/tseaver/orgs","repos_url":"https://api.github.com/users/tseaver/repos","events_url":"https://api.github.com/users/tseaver/events{/privacy}","received_events_url":"https://api.github.com/users/tseaver/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/zopefoundation/zope.component/labels/bug","name":"bug","color":"fc2929"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-01-26T20:06:33Z","updated_at":"2015-01-26T20:06:33Z","closed_at":null,"body":"In https://bugs.launchpad.net/zope.component/+bug/1181749, @djay reported:\r\n\r\n> If there is an exception in the factory when creating the adapter, `zope.component` will silently move on to the next adapter and eventually give a \"could not adapt\" error. This makes it very hard to debug such an error since you first have to guess what factories might be being called and then guess where the exception could be coming from. Is there a way we could have more meaningful stacktrace or logs which give clues to the swallowed exception?"}}