`report()` may set wrong `handled` property

[cleptric]

Thanks! Can confirm the patch fixed it.

All exceptions are now reported as unhandled. Even the ones manually logged through Laravel's report() helper – which I use to 'soft'-report exceptions that didn't crash the application. How did you intend to make a distinction between handled and unhandled exceptions? Laravel doesn't have a concept of handled vs. unhandled exceptions.

Originally posted by @devfrey in #608 (comment)

[cleptric]

Our goal was to introduce a distinction between errors sent via captureException() handled: true and errors caught by the global error handler of the framework handled: false.

https://laravel.com/docs/9.x/errors#the-report-helper

public function isValid($value)
{
    try {
        // Validate the value...
    } catch (Throwable $e) {
        \Sentry\captureException($e); // handled: true
 
        return false;
    }
}

It's a bit unfortunate that report() behaves that way. So we may have to make a decision on how to handle this going forward.
Having handled: false is highly valuable, as it highlights the errors with higher priority IMO.