Stefano Arlandini

I've encoutered the same problem and not finding this issue (I will look better next time, I promise 😄) I proposed a different solution, which is simpler. I quote it...

> That is what the bubble was meant to do: If the message is handled (based on level usually), then it should false if bubbling is allowed, so other handlers...

I agree with @Jean85. Coding-wise, this PR looks perfect, but the usefulness of this change is a mistery for me. Why adding a new option, increasing the complexity of the...

This is a good question that went unnoticed 😞 As an OSS contributor to this project I don't have the answer. @mitsuhiko maybe you have some details that you want/can...

You can disable the retrying of events by setting the `send_attempts` to `0`

>we still have the remaining question whether the default behavior makes sense for PHP In the past version `2.x`, the sending of the events was delayed until the shutdown of...

Besides updating (and maybe requiring a minimum version of the package to avoid such issues?), I think it would be more appropriate also to handle 429 limits well, as I...

>in PHP it could download the code and spawn a process Please, no! Whatever thing downloads and installs things in the background without the user consent should be treated as...

I see one issue with the current implementation: in case of an exception thrown by the HTTP client, we are already logging the error. With the proposed change, we would...

There's no reason to not support this now that the server does, however I have no ETA to share on when this will happen, if it will. _Disclaimer: I'm not...