Grégoire Paris

> Hmm, perhaps we could change the verbosity to be higher by default? Definitely 👍 [one level should be enough to display a stack trace](https://symfony.com/doc/current/contributing/code/stack_trace.html#stack-traces-in-the-cli)

I think you would do that here, by messing with the currently not provided `$input` argument: https://github.com/laminas/automatic-releases/blob/2008a9e98f65c0dcacb90eabb4d12987080ed1d7/bin/console.php#L168 See https://github.com/symfony/console/blob/3b597067ee2b07ef6fbbebfe2afa0e88fae9a8a7/Application.php#L904-L926 A typical `bin/console` of a symfony app looks like this (excerpt):...

> You'd need to add -vvv to the commands being run: I don't think any other env variables are being considered at all. What about https://github.com/laminas/automatic-releases/issues/78#issuecomment-706596751 ?

Since you added some troubleshooting commits on top of 2.7.x, the message is correct I think. I don't understand why the tag was not created on the tip of the...

See https://github.com/laminas/automatic-releases/issues/78#issuecomment-706596751 , how about putting `SHELL_VERBOSITY=3` in the env if not already defined?

@drupol what's your take on https://www.dragonbe.com/2015/07/speeding-up-database-calls-with-pdo-and.html ?

I do not confirm and I reject the burden of proof :stuck_out_tongue:

IMO the most BC way would be to add a new array, and cache exceptions in that array, that way you are sure to throw the same type of exception...

> The code does not properly handle cases where code implements the Proxy interface without the future methods I see several paths forward: 1. deprecate the `Proxy` interface in favor...

I went ahead and implemented a check, but just for the methods that are called.