-
Notifications
You must be signed in to change notification settings - Fork 130
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
Getting error after updating to #55c3f875f08a333848284cdbc1fd3e0cea4e6776 #287
Comments
@gremo please help |
@mzampetakis can you please provide the output of the same command with the |
|
|
@greg0ire are you sure it depends on my commit? |
No I have no clue. @mzampetakis please use |
I have never used git bisect. Can you guide me please? |
If you have access to the sf slack please have a look at this conversation I had about bisecting: https://symfony-devs.slack.com/archives/C3GC7MKM5/p1506013758000022 (I should really write a blog post or something someday). |
And if you don't, https://symfony.com/slack-invite should get you in |
I will try to bisect it later. However, going back to #4adca6ba4feec25869c16a8af2ade9f20fc62f91 worked fine. I indeed use sf 2.8. |
482fdb8 Seems to be the problematic one.
If I comment the |
@adaniloff maybe because of this https://github.com/symfony/finder/blob/master/Finder.php#L566 @mzampetakis do you have Before my commit, all bundles where scanned. That is, the Finder component received at least one directory to scan. Now, this isn't true all the time. Honestly, I was not aware of exception thrown in case of empty directories to scan. |
@gremo, I don't know what these configurations are (all_bundles: false and bundles: []). |
@mzampetakis can you past your JMSDiExtraBundle configuration? |
@gremo my config
|
@mzampetakis thank you, I'll look and do some tests ASAP. |
Can't tell. I cannot check it up rightnow. I'll tell as soon as I can. Thanks for the help anyway. |
After updating to commit#55c3f875f08a333848284cdbc1fd3e0cea4e6776
I get this error while clearing my cache:
Going back to #4adca6ba4feec25869c16a8af2ade9f20fc62f91 it worked fine.
The text was updated successfully, but these errors were encountered: