-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
The folder named r+e.gex[c]a(r)s breaks our build #13350
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Centos |
Could you paste the full error message? Also, is it a Symfony test failing or yours? |
We use a grunt plugin that wraps the creation of RPMs called easy_rpm, it's running this on our CI that's failing. We're not running the Symfony tests as part of the build. If we remove the r+e.gex[c]a(r)s folder before the following step then the RPM creation works. Running "easy_rpm:dist" (easy_rpm) task |
It looks like a bug in the easy_rpm plugin, not Symfony. |
Fair enough. It is a strange name for a folder but I suppose r+e.gex[c]a(r)s is a valid. I'd consider finding another way to test this though as it's likely to cause other strange issues: it's probably best to stick to upper, lowercase ".", "_". Happy to close though. |
It was implemented to fix a specific issue (#11970), and checking for lowercase ".", "_" is not enough in this case. I'd advice to try fixing the easy_rpm plugin first, and if that fails, reopen this issue with proposition how to solve it differently. |
Getting a similar error while uploading the laravel app to Google App Engine. ERROR appcfg.py:1909 Invalid character in filename: vendor/symfony/finder/Tests/Fixtures/r+e.gex[c]a(r)s/dir/bar.dat |
Also getting the same error as @JunaidBabu: |
Yes, and it also makes stress with svn... Regards, |
We run rpmbuild as part of our build process and the folder /src/Symfony/Component/Finder/Tests/Fixtures/r+e.gex[c]a(r)s/ seems to be linked to a "error: File not found by glob: ..." error. Presumably the some character in the folder name is being treated as a wild card or something strange?
The text was updated successfully, but these errors were encountered: