What are the Slack Archives?
Itβs a history of our time together in the Slack Community! Thereβs a ton of knowledge in here, so feel free to search through the archives for a possible answer to your question.
Because this space is not active, you wonβt be able to create a new post or comment here. If you have a question or want to start a discussion about something, head over to our categories and pick one to post in! You can always refer back to a post from Slack Archives if needed; just copy the link to use it as a reference..
Hello Everybody, I've upgraded ``merchant-custom-prices`` feature : `php -d memory_limit=-1 /usr/loc
Hello Everybody,
I've upgraded merchant-custom-prices feature :php -d memory_limit=-1 /usr/local/bin/composer require "spryker-feature/merchant-custom-prices:^202009.0" --update-with-dependencies
As a next step I wanted to do console propel:install but faced an issue (attached).
Is this something you saw before?
Comments
-
It might be that I'm wrong, but similar issues were discussed internally and the solution was to try to lock
symfony/filesystem: 5.1.8.0 -
Thanks, I'll check that.
0 -
Valerii, we're using "feature" approach in composer.json where there is no
symfony/filesystempackage. Do you have the same case?0 -
giovanni.piemontese Technical Lead @ LΓΆffelhardt Spryker Solution Partner Posts: 871 π§π»βπ - Cadetsymfony/filesystem: 5.1.8v. 5.1.10 it will be releases at end of this month0 -
giovanni.piemontese Technical Lead @ LΓΆffelhardt Spryker Solution Partner Posts: 871 π§π»βπ - Cadet
composer required symfony/filesystem: 5.1.8to constraint... when 5.1.10 released, then remove this constraint and runcomposer update0 -
Shall I use composer update or composer require ?
0 -
giovanni.piemontese Technical Lead @ LΓΆffelhardt Spryker Solution Partner Posts: 871 π§π»βπ - Cadet
composer require.. u have to constraint the package
0 -
Let me check.
0 -
Problem 1 - spryker-sdk/spryk 0.2.3 requires symfony/filesystem ^3.4.0 || ^4.0.0 -> satisfiable by symfony/filesystem[3.4.x-dev, 4.0.x-dev, 4.1.x-dev, 4.2.x-dev, 4.3.x-dev, 4.4.x-dev]. - spryker-sdk/spryk 0.2.3 requires symfony/filesystem ^3.4.0 || ^4.0.0 -> satisfiable by symfony/filesystem[3.4.x-dev, 4.0.x-dev, 4.1.x-dev, 4.2.x-dev, 4.3.x-dev, 4.4.x-dev]. - spryker-sdk/spryk 0.2.3 requires symfony/filesystem ^3.4.0 || ^4.0.0 -> satisfiable by symfony/filesystem[3.4.x-dev, 4.0.x-dev, 4.1.x-dev, 4.2.x-dev, 4.3.x-dev, 4.4.x-dev]. - Can only install one of: symfony/filesystem[v5.1.8, 3.4.x-dev]. - Can only install one of: symfony/filesystem[v5.1.8, 4.0.x-dev]. - Can only install one of: symfony/filesystem[v5.1.8, 4.1.x-dev]. - Can only install one of: symfony/filesystem[v5.1.8, 4.2.x-dev]. - Can only install one of: symfony/filesystem[v5.1.8, 4.3.x-dev]. - Can only install one of: symfony/filesystem[v5.1.8, 4.4.x-dev]. - Installation request for symfony/filesystem 5.1.8 -> satisfiable by symfony/filesystem[v5.1.8]. - Installation request for spryker-sdk/spryk (locked at 0.2.3) -> satisfiable by spryker-sdk/spryk[0.2.3].0 -
Unfortunately I'm blocked. Any ideas?
0 -
giovanni.piemontese Technical Lead @ LΓΆffelhardt Spryker Solution Partner Posts: 871 π§π»βπ - Cadet
U have to update spryker sdk packages
0 -
giovanni.piemontese Technical Lead @ LΓΆffelhardt Spryker Solution Partner Posts: 871 π§π»βπ - Cadet
Or sorry with βupdate dependencies
0 -
I ended up in a situation where I should update
spryker/symfony0 -
I cannot do that.
0 -
Then it might be no the same problem as was discussed internally. But it looked very similar:
Command propel-copy-schema [vendor/bin/console propel:schema:copy] (In progress...) Store: DE | Environment: docker Clean schema directory Copy and merge schema files ErrorException - Exception: unlink(/data/src/Orm/Propel/DE/Schema/spy_acl.schema.xmlJglEnD): No such file or directory in /data/vendor/symfony/filesystem/Filesystem.php (670)
0 -
Or you are on the previous major of symfony/filesystem. Could you check please your composer.lock file?
In case you are on v3 or v4, there were also new releases that could cause this problem and you need to roll back to the previous one.0 -
yeah what I did is temporarily hacked ErrorHandlerEnvironment
0 -
the problem is that it does not respect silenced errors
0 -
and still throw exceptions
0 -
so quick and dirty way is to just replace
setErrorHandlermethodwith
/** * @return void * @throws \ErrorException */ protected function setErrorHandler(): void { $errorLevel = error_reporting(); $errorHandler = static function ($severity, $message, $file, $line): void { $exception = new ErrorException($message, 0, $severity, $file, $line); $levelsNotThrowingExceptions = Config::get(ErrorHandlerConstants::ERROR_LEVEL_LOG_ONLY, 0); // is exceptions silenced with @ $isSilenced = error_reporting() === 0; $shouldThrowException = ($severity & $levelsNotThrowingExceptions) === 0 && !$isSilenced; if ($shouldThrowException) { throw $exception; } // Only log non-silenced errors if (!$isSilenced) { ErrorLogger::getInstance()->log($exception); } }; set_error_handler($errorHandler, $errorLevel); }This way the composer or propel command will finish
0 -
-
For those who had problems with symfony/filesystem, it seems that new versions with fixes were released. So you can update it to 5.2.1 or 4.4.18 or 5.1.10
0 -
giovanni.piemontese Technical Lead @ LΓΆffelhardt Spryker Solution Partner Posts: 871 π§π»βπ - Cadet
Danke Valerii!
0
Categories
- All Categories
- 42 Getting Started & Guidelines
- 7 Getting Started in the Community
- 8 Additional Resources
- 7 Community Ideas and Feedback
- 84 Spryker News
- 975 Developer Corner
- 827 Spryker Development
- 91 Spryker Dev Environment
- 362 Spryker Releases
- 3 Oryx frontend framework
- 36 Propel ORM
- 68 Community Projects
- 3 Community Ideation Board
- 30 Hackathon
- 3 PHP Bridge
- 6 Gacela Project
- 31 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
- 33 Product & Business Questions
- 70 Spryker Safari Questions
- 50 Random