Skip to content
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

[5.3] dont report exception inside signal handler #16738

Merged
merged 1 commit into from
Dec 10, 2016

Conversation

halaei
Copy link
Contributor

@halaei halaei commented Dec 10, 2016

The reasons to keep signal handler simple:

  1. The timed-out job will be retried later and if the number of attempts exceeds, it will be reported. Therefore, reporting here is redundant.
  2. The reporting process may get stuck forever because of network errors - for example if Bugsnag is used. I am not sure it is possible to register another signal handler inside this one to prevent the issue.

@taylorotwell taylorotwell merged commit afccec3 into laravel:5.3 Dec 10, 2016
@GrahamCampbell GrahamCampbell changed the title dont report exception inside signal handler [5.3] dont report exception inside signal handler Dec 10, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants