Alessandro Lai
Alessandro Lai
Reason found: attacching the handler to `monolog.logger` is not enough, that's just the logger for the default channel (normally `app`). We would need to add the handler to all the...
@nicolas-grekas, since you were the first in suggesting this approach of attaching Sentry to Monolog in #337, do you have any suggestion to solve this issue? :point_down: Or can you...
The behavior of the HTTP layer is unfortunately out of our control. Maybe switching to Guzzle would make those errors bubble up? BTW these errors would surface better with https://github.com/getsentry/sentry-php/pull/989,...
Ouch, I forgot about the delayed sending. In the next major version that will be no longer the default behaviour, but we need to fix it here. Maybe we can...
@ste93cry is this still needed with 4.0?
#372 seems related to this.
This is probably due to something on the Monolog bundle side that our. See https://github.com/symfony/monolog-bundle/pull/393 which is included in 3.7.0. See also https://github.com/symfony/monolog-bundle/pull/394 which is in the same tag, and...
It surely may depend on that. Config is parsed and dumped in the cache, so if that doesn't get refreshed, you're right, your tests are invalid.
I personally do the opposite, so this bundle still has merit. As for this feature, I would imagine that this feature should be done using the Breadcrumbs. So, what we...
This should be taken into consideration while working on #337