Michi Hoffmann

According to https://github.com/curl/curl/issues/11175#issuecomment-1559739707 it is

We indeed use this plugin directly, https://github.com/getsentry/sentry-php/blob/master/src/HttpClient/HttpClientFactory.php#L102.

We worked around this issue by enforcing HTTP/1.1 for now. I still suggest finding a proper solution, as we will be one of many running into this issue.

We are currently working on an entirely new User Feedback product, which is tied together with Session Replays. The feature is currently in a closed Alpha. There is a bit...

While I'm not having the historical context of why this was implemented like that, I noticed that gin's context relies on strings for `Get()` and `Set()`, while our `HubContextKey` is...

Most of this sounds reasonable, but this is sadly out of scope. I can only focus on the Symfony SDK for a short amount of time at the moment, hence...

There are some tools like https://github.com/symplify/monorepo-builder that make this possible. Not going to add more PHP repositories, sorry.

Ok, then I'll move forward with a slim v5.0. Thanks! > However, since by default everything is enabled, even if the event is eventually discarded, all the collection is still...

https://docs.sentry.io/platforms/php/guides/symfony/performance/instrumentation/automatic-instrumentation/ > But right now, it makes no sense because it takes away people's free will, and history teaches it's never a good thing. lol

We are not changing that.