{"action":"opened","issue":{"url":"https://api.github.com/repos/alimanfoo/petl/issues/365","labels_url":"https://api.github.com/repos/alimanfoo/petl/issues/365/labels{/name}","comments_url":"https://api.github.com/repos/alimanfoo/petl/issues/365/comments","events_url":"https://api.github.com/repos/alimanfoo/petl/issues/365/events","html_url":"https://github.com/alimanfoo/petl/issues/365","id":127284719,"number":365,"title":"convert() and fieldmap() swallow errors silently by default","user":{"login":"thatneat","id":3341011,"avatar_url":"https://avatars.githubusercontent.com/u/3341011?v=3","gravatar_id":"","url":"https://api.github.com/users/thatneat","html_url":"https://github.com/thatneat","followers_url":"https://api.github.com/users/thatneat/followers","following_url":"https://api.github.com/users/thatneat/following{/other_user}","gists_url":"https://api.github.com/users/thatneat/gists{/gist_id}","starred_url":"https://api.github.com/users/thatneat/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/thatneat/subscriptions","organizations_url":"https://api.github.com/users/thatneat/orgs","repos_url":"https://api.github.com/users/thatneat/repos","events_url":"https://api.github.com/users/thatneat/events{/privacy}","received_events_url":"https://api.github.com/users/thatneat/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2016-01-18T18:25:52Z","updated_at":"2016-01-18T18:25:52Z","closed_at":null,"body":"This has led to a lot of difficult-to-debug scenarios in my experience. \r\nAs you're developing an ETL pipeline, you're often iterating on your conversion functions quickly, which often leads to exceptions being raised. Currently petl eats those errors silently, making it far more difficult to navigate this process.\r\nIn the regular operation of an ETL pipeline, it's also undesirable for new, unexpected errors to pass silently.\r\n\r\nThe current workaround is to set `failonerror=True` in every call to `fieldmap()` and the like. I suggest you make `failonerror=True` be the default. This might be something that would require bumping to version 2.0 since it will likely cause a lot of exceptions to be raised that were previously ignored (for better or for worse!)."}}