FYI: symfony/filesystem version 6.4.7 breaks some console commands
For example propel:install fails with
ErrorException - Exception: fileperms(): stat failed for /data/src/Orm/Propel/Schema//spy_acl.schema.xml
This is because of
using the STFU operator @ to silence fileperms() in vendor/symfony/filesystem/Filesystem.php:689 and from what I understand, Spryker's error handler doesn't like that(?)Comments
-
Yes, for us too.. We had to constraint temporarly to 6.4.6
0 -
fsmeier Senior Software Engineer & Developer Enablement Advocate Sprykee Posts: 1,056 ⚖️ - Guardians (admin)
Heyhey,
does this happen with the ootb demoshop or after updating packages individually?Can you provide me more information about how to reproduce it?
+ it always helps to also create an official support case so I can better push the prio :)
All the best,
Florian
0 -
Same for us.
To fix it we've added the E_WARNING to the error level log only list.
# default_config.php $config[ErrorHandlerConstants::ERROR_LEVEL_LOG_ONLY] = E_DEPRECATED | E_USER_DEPRECATED | E_WARNING;
The downside is that these warnings are now being logged in the deployment pipelines and jenkins logs.
0 -
Based on PR
for Symfony 5.4 there's a pretty good chance they'll also fix/change that for 6.4.Offtopic but related: I have very little understanding of how different error levels work, but apparently I had at some point added a custom config (default_config.php):
// This is a custom solution to keep deprecation messages from filling the logs
// -Mikko
$config[ErrorHandlerConstants::ERROR_LEVEL_DO_NOT_LOG] = E_DEPRECATED | E_USER_DEPRECATED;and used that to wrap error logging in \Pyz\Shared\ErrorHandler\ErrorHandlerEnvironment::setErrorHandler like:
$doNotLogLevels = Config::get(ErrorHandlerConstants::ERROR_LEVEL_DO_NOT_LOG, 0);
if (($severity & $doNotLogLevels) === 0) {
ErrorLogger::getInstance()->log($exception);
}Sorry for the formatting.
0 -
fsmeier Senior Software Engineer & Developer Enablement Advocate Sprykee Posts: 1,056 ⚖️ - Guardians (admin)
Heyhey, me again :)
Can you provide me more information about how to reproduce it in the ootb demoshop?All the best,
Florian
0 -
Should be just
docker/sdk cli composer update
ordocker/sdk cli composer require symfony/filesystem:6.4.7
and then
docker/sdk console propel:install
starts failing. Or I think more accurately propel:schema:copy is the step that does the thing in filesystem.
0 -
Fix was released from symfony →
1 -
fsmeier Senior Software Engineer & Developer Enablement Advocate Sprykee Posts: 1,056 ⚖️ - Guardians (admin)
Heyhey,
so I followed @mikko.ropanen s steps now to reproduce and it seems to be fixed with the latest release as @ynnoig was mentioning 🙌Thank you all for your input! I love this collaboration in the community!!
Have a nice day,
all the best,
Florian
0
Categories
- All Categories
- 42 Getting Started & Guidelines
- 7 Getting Started in the Community
- 8 Additional Resources
- 7 Community Ideas and Feedback
- 69 Spryker News
- 896 Developer Corner
- 758 Spryker Development
- 83 Spryker Dev Environment
- 361 Spryker Releases
- 3 Oryx frontend framework
- 34 Propel ORM
- 68 Community Projects
- 3 Community Ideation Board
- 30 Hackathon
- 3 PHP Bridge
- 6 Gacela Project
- 23 Job Opportunities
- 3.2K 📜 Slack Archives
- 116 Academy
- 5 Business Users
- 370 Docker
- 551 Slack General
- 2K Help
- 75 Knowledge Sharing
- 6 Random Stuff
- 4 Code Testing
- 32 Product & Business Questions
- 68 Spryker Safari Questions
- 50 Random