An error after updating

[iranimij]

After updating I get below error :

Unable to find path for module "Magento_Framework"

[jissereitsma]

I've tried various commands on my end and it all works just fine. Which command fails with this output? And is this indeed version 2.5.10?

[iranimij]

@jissereitsma This command

bin/magento yireo_extensionchecker:scan --module $(bin/magento module:status --enabled | grep Test_ | awk '{printf "%s%s",sep,$0; sep=","} END{print""}') --hide-needless 1 --hide-deprecated --skip-license-check 1

Yes, it is ok with 2.5.9 and problematic with 2.5.10

[jissereitsma]

Hmm, this still is something I can't reproduce. Note that the subcommand bin/magento module:status --enabled | grep Test_ | awk '{printf "%s%s",sep,$0; sep=","} END{print""}' is not relevant here. That's just how you get to a specific module name. Could you double-check that that command actually outputs a specific module name that you wanted to check for? In my case, this does not match any modules, but that's because none of the modules in my environment are containing the string Test_.

So I assume that this problem is reproducable with a specific module ExampleTest_Example (replace this with your own module) that you have. Could you confirm that the following command indeed gives this error?

bin/magento yireo_extensionchecker:scan --module ExampleTest_Example

If so, could you run the following command and post its output:

bin/magento yireo_extensionchecker:list-dependencies --module ExampleTest_Example | grep -i framework

[iranimij]

bin/magento yireo_extensionchecker:scan --module ExampleTest_Example

The above code does not return any errors, although when I have a list of modules, it returns errors. The point is that if I downgrade the module, it works fine. So it is absolutely the new version's issue.

[jissereitsma]

There would still be a single module that generates this error. On my end, I'm trying my best to duplicate things, but the error is not thrown for any of my modules. So unless I'm able to duplicate the problem, I don't what to do.

The following commit seems to be causing the feedback: bb7d178 But, indeed a module Magento_Framework should never exist, right?

[iranimij]

@jissereitsma You are right, we should never use Magento_Framework, But do you think it is the best way?
Previous version, it was ok having 'Magento_Framework' , after updating the module without changing any dependencies, we see there are some errors. although we have the flag --hide-needless. I think we need to at least take care of this flag.