You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The reason will be displayed to describe this comment to others. Learn more.
@connorhu with this change the autoload will fail, because this files are hardcoded in sfCoreAutoload.class.php vendor/friendsofsymfony1/symfony1/lib/autoload/sfCoreAutoload.class.php
The reason will be displayed to describe this comment to others. Learn more.
Its: php symfony PHP Warning: require(/xxxx/vendor/friendsofsymfony1/symfony1/lib/task/test/sfTestPluginTask.class.php): Failed to open stream: No such file or directory in /xxxx/vendor/friendsofsymfony1/symfony1/lib/autoload/sfCoreAutoload.class.php on line 451 PHP Fatal error: Uncaught Error: Failed opening required '/xxxx/vendor/friendsofsymfony1/symfony1/lib/task/test/sfTestPluginTask.class.php' (include_path='.:/usr/share/php') in /xxxx/vendor/friendsofsymfony1/symfony1/lib/autoload/sfCoreAutoload.class.php:451 Stack trace: #0 [internal function]: sfCoreAutoload->autoload()
The reason will be displayed to describe this comment to others. Learn more.
@thePanz I'm not sure it would have caught it when just testing the project, because just cloning the repo will not exclude the test dir. The issue is that composer evaluates .gitattributes when installing dependencies and removes files/directories listed as export-ignore when installed as a dependency of another project.
3f0adca
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@connorhu with this change the autoload will fail, because this files are hardcoded in
sfCoreAutoload.class.php
vendor/friendsofsymfony1/symfony1/lib/autoload/sfCoreAutoload.class.php
3f0adca
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Its:
php symfony PHP Warning: require(/xxxx/vendor/friendsofsymfony1/symfony1/lib/task/test/sfTestPluginTask.class.php): Failed to open stream: No such file or directory in /xxxx/vendor/friendsofsymfony1/symfony1/lib/autoload/sfCoreAutoload.class.php on line 451 PHP Fatal error: Uncaught Error: Failed opening required '/xxxx/vendor/friendsofsymfony1/symfony1/lib/task/test/sfTestPluginTask.class.php' (include_path='.:/usr/share/php') in /xxxx/vendor/friendsofsymfony1/symfony1/lib/autoload/sfCoreAutoload.class.php:451 Stack trace: #0 [internal function]: sfCoreAutoload->autoload()
3f0adca
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@thePanz @alquerci This change should be reverted, as it removes the
test
directory from thesymfony1/lib
dir.Internal error: Failed opening required '/path/to/friendsofsymfony1/symfony1/lib/test/sfTestFunctional.class.php'
3f0adca
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hello @iricketson
The revert is already done, at least fixes the issue you exposed.
7afe4d2
3f0adca
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@alquerci @thePanz Can we tag
1.5.21
due to breaking change?3f0adca
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@iricketson I will give it a try today to tag a new release.
How did you use SF1 to trigger that error? @JohannesTyra @iricketson
See my comment here: #379 (comment)
do you use plain SF1 or wrap it in a newer SF version?
3f0adca
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@thePanz I use plain SF1 and while
php symfony cc
or other tasks, the errors occurs.3f0adca
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@thePanz Running
phpstan
caught it after updating the dependencies. Not wrapped.My guess is it is trying to evaluate lime tests that instantiate symfony functional testing, like so:
3f0adca
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@iricketson @JohannesTyra I tagged v1.5.21, let me know if this helps to solve your issues
thanks for the clarifications!
it would be interesting to include phpstan to test the project, maybe those issues could have been identified earlier?
3f0adca
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@thePanz I'm not sure it would have caught it when just testing the project, because just cloning the repo will not exclude the
test
dir. The issue is that composer evaluates .gitattributes when installing dependencies and removes files/directories listed asexport-ignore
when installed as a dependency of another project.3f0adca
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@iricketson yeah, I am aware of the way composer installs libs from Git repositories (via the
git archive
)Maybe a solution would be to have a pipeline running
composer inst
on a dummy project, and testing it there 🤔3f0adca
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@thePanz its working! The files I mentioned (and are needed) are back again ;)