-
-
Notifications
You must be signed in to change notification settings - Fork 451
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
Exceptions go to Sentry but not to log file for application #468
Comments
OK looks like it's fixed in 1.7.0 (#421) https://github.com/getsentry/sentry-php/blob/master/CHANGELOG.md This is a pretty bad regression IMO, any idea when that will be officially tagged? |
I think only @dcramer can answer this.. |
Fwiw we don't consider this a regression as behavior never existed before. @Jean85 I can write up general docs on how I prepare releases if you're interested in shipping 1.7.0? |
@dcramer absolutely! Let us know how the flow works; I imagine that you still have to authorize a new release, but we still can do all the heavy lifting for you ;) |
I'm going to close this out, but we'll get 1.7.0 out by EOW. |
That's great news, thanks. |
Any ETA on when 1.7.0 will be going out? |
@vbjordan sorry about that, shoudl be live now |
Currently using version 1.6.2 of sentry-php as a composer dependency and I'm seeing this issue with the library:
https://stackoverflow.com/questions/35274672/empty-php-logs-when-using-sentry
So an exception gets sent to Sentry, but the error message doesn't go to the log for the application. Is this a known issue? Is there a workaround or some configuration that needs to be set?
The text was updated successfully, but these errors were encountered: