You must turn off the xdebug.scream PHP.ini setting.

This is intentioned? How can we use xdebug to debug our application when developing with this silenced functions? xdebug.scream = 1 Cause Symfony unable to use when developing...

Thanks!

you don't need xdebug.scream, silenced errors are already reported in log files and in the "log" profiler panel

But this is not flexible, we need to upgrade the error reporting level, the @ for us is a very bad practice, so we with xdebug.scream enabled knew when someone uses in our controllers, services etc...

A forced Exception is our current solution in 2.8 and works great as expected, with a new project of 4.0 this is not possible.

The tab 'log' panel doesn't show an exception to the programmer, is only a simple logline that nobody reads. There is a setting to enable exceptions for the @ in the src directory? I think no... so, forced to hide behind the carpet all silenced functions with the @is a very very bad solution... IMHO.

🤔

this is PHP, the silencing operator is mandatory in some situations, this is one of them, there are more, mostly related to filesystem functions

@lemenendez proposed a solution for this, but you close the issue.

I'm really sorry if I sound rude but there is a lot of checks to solve the usage of @ (like file_exists in the above case) in any context and any situation, we live without @ since PHP 3.

Is for performance reasons? Ok, but the container only compiles at once, so the use of file_exists in favor of removing the bad @ operator IMHO is justified to solve this issue.

Anyway is your framework, your rules (community?). Any help here is welcome, we never use the @ operator because is a very ugly bad practice (use defensive programming first, error last).

Thanks anyway.

Maybe wrapping this one in a file_exists() check would do it here, optimistically. But the @ would still be required, and in many other places, to prevent any race conditions. In other cases, (eg #26013), the extra check has been proven a perf killer.
So in the end, it does not make sense to support running with xdebug.scream on.
It's already required to be off by the requirements-checker btw (see https://symfony.com/doc/current/reference/requirements.html)

50% agree, with OPCache file exists only reads in memory.

But with new requirements for 4.0 this issue make no sense!

Many thanks @nicolas-grekas!