New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Increase error severity in dispatcher's call handler #16

Merged
merged 1 commit into from Nov 1, 2015

Conversation

Projects
None yet
2 participants
@paultcochrane
Contributor

paultcochrane commented Nov 1, 2015

As per the comment in GitHub issue #4, it was recommended to increase the
error severity to FATAL rather than WARN. This uses confess as mentioned
in the ticket, however I'm unsure if this is sufficient to completely
address the bug.

Increase error severity in dispatcher's call handler
As per the comment in GitHub issue #4, it was recommended to increase the
error severity to FATAL rather than WARN.  This uses `confess` as mentioned
in the ticket, however I'm unsure if this is sufficient to completely
address the bug.

chiselwright added a commit that referenced this pull request Nov 1, 2015

Merge pull request #16 from paultcochrane/pr/increase-error-severity-…
…in-call-handler

Increase error severity in dispatcher's call handler

@chiselwright chiselwright merged commit 8e0905c into chiselwright:master Nov 1, 2015

chiselwright added a commit that referenced this pull request Nov 15, 2015

v0.0.5
 - Merged pull-requests from Paul Cochrane:
   - #6 replace NoTabsTests
   - #7 add missing abstracts (for dzil)
   - #8 add Travis config
   - #9 purge trailing whitespace
   - #10 fix POD errors
   - #11 update dist.ini
   - #12 add missing strictures
   - #13 remove shebang in tests
   - #14 fix typos in POD
   - #15 fix tests on non-English locales
   - #16 increase error severity in call handler
 - Resolve "[PkgVersion] no blank line for $VERSION after package" with dzil prep
 - add skeleton POD for methods
   unhelpfully empty but keeps pod-coverage tests happy
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment