Michael Olšavský

@labbati Great news, thank you! Offering a block_list of span names sounds like a good enough solution for most use-cases. Regarding the Integration::toString, yes, we're using it to set tags...

Perhaps in our case, we can get rid of the Tracer->reset() call. Anyway, I thought it's worth considering and at least documenting for others :)

We actually had to implement our own retry layer due to this issue. @frankdejonge Any problems with this solution? I can rebase it on v2.

```php use League\Flysystem\PhpseclibV2\ConnectivityChecker; use phpseclib\Net\SFTP; class SftpPingConnectivityChecker implements ConnectivityChecker { public function isConnected(SFTP $connection): bool { return $connection->ping() && $connection->isConnected(); } } ``` @kiropowered We just register our own connectivity...

I found and issue with registration of error handlers in Illuminate\Foundation\Bootstrap\HandleException. I tried to fix it in https://github.com/laravel/framework/pull/44293 but it's not trivial (as already stated in the original MR https://github.com/laravel/framework/pull/40656#issuecomment-1022954055)....

Ideally as a phpunit element attribute in the XMLConfiguration. ``` ... ``` I see that the Exporter is being created in a lot of different places, especially in the `\PHPUnit\Framework\Constraint\Constraint::exporter()`...

Good point, thank you!

Hi @IvanGoncharov, I see this issue in the 16.0.0-alpha.1 milestone which has already been released. Is it still planned for the v16 or did you come over to some issues...

@hamzahamidi Can you elaborate on this? I can't think of such situation as I'm not saying to run these resolvers in sequence but rather just way for all resolvers to...

We have the very same use case with AWS Aurora (dynamic number of read replicas so in order to use both connection pool and discover new hosts, we need to...