aand18

@Jean85 I think this loop already can already happen in `HttpTransport`: https://github.com/getsentry/sentry-php/blob/5b611e3f09035f5ad5edf494443e3236bd5ea482/src/Transport/HttpTransport.php#L125-L135 I'm not sure there's a use case for logging library messages to Sentry, sounds like a recipe for...

> 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...

> Of course, it doesn't make sense to report errors to Sentry if the library itself errored. The logger was put in place as a sort of fallback, so that...

@stof I'd say `stdClass`, as PHP already uses that by default when casting to `object`: ```php echo get_class((object) []); // "stdClass" ```

> Hey, thanks for your report! There has not been a lot of activity here for a while. Is this bug still relevant? Have you managed to find a workaround?...

Wow! It would be nice if this got merged!

Hi @amaelftah , make sure `APP_ENV` is not `testing` (for example print `env('APP_ENV')` in your app. It can happen that system values, for example, will override `.env` file values. See...

That's because you also have installed the forked plug-in with this fix: https://github.com/bluelovers/ZeroLengthRadar/commit/c8a718a374c1a7cea9279c24e7e76eaabd2c80d5 You should uninstall one of the two plug-ins.