Alessandro Lai
Alessandro Lai
> This will require us to be stricter about the commit messages, but this is already encouraged. Since we do squash-merge on PRs, that shouldn't be too hard. > Like...
This is another issue that would be solved by #337. It's possible that your app config is somewhat messing with Symfony's error handler, so I don't think we can do...
Interesting! Can you please add tests and a changelog entry for this?
Thank you for opening the PR, but this is unmergeable without tests, a green build and a changelog entry.
The point is that by default (and by design as said in ) we do not copy context from Monolog in the base SDK. So we need a basic example...
Yes I meant specific code related to Monolog. Ok I've dug a bit here and there, and here's what I've found: * there's a 3rd party package to do it...
Why do you think it's pointless? It seems to me that people are just trying to avoid duplication, by tying Sentry to Monolog and logging just once, but getting the...
:+1: on this one. I had my whole worker setup crash in a loop due to this. This is super critical, I had to: * scale the workers x5 to...
Pinging @Nyholm @jderusse because this is tightly related to their Async-AWS package solution.
That's probably the main core of the issue: it's hard to pin down a possible approach or workaround, because the issue rises at the end of the process, after the...