Alessandro Lai
Alessandro Lai
No you're right, Paraunit's behavior was like this since the previous major, and now PHPUnit started handling deprecations explicitly and we didn't align it to that. It probably makes sense...
This is probably due to the fact that PHPUnit splits the failure message in multiple pieces on the inside. Depending of which PHPUnit version is in use, Paraunit fetches the...
This may require a change in the spec..
Yes you found the correct bottleneck: I use the Composer API to reach into `installed.php` and obtain the needed info. I've tried reproducing the Sentry use case in a naked...
I'm still affected by this, any way to fix it?
This would have to be done by parsing the Markdown of the document, which I'm not sure it's feasible.. We use Commonmark to translate the documents in proper HTML.
Styling should also keep in mind mobile... And that's a bit hard :sweat: any frontender can lend a hand here?
This is done in https://github.com/php-fig/www.php-fig.org/ using spatie/commonmark-highlighter: https://github.com/php-fig/www.php-fig.org/blob/d4e8ce81affa552f1b62da5fe3e35a802701710d/composer.json#L9 I'm moving this issue in that repo. It's fairly new syntax, I don't know if that package supports that already (and we...
Why caching? Wouldn't be enough to trigger that earlier, i.e. on `kernel.request`? Or even better, on-demand? We may need to investigate side-effects...
I would vote toward clearing by default: a memory leak or an event too fat to be received by Sentry would be around the corner otherwise. The only safeguard would...