Module configuration not working in monorepo of multiple modules

[Jonny Power (he/him)]

Hi,

I have a module in a project, that has the IC2 facet, with connections configured, and with an offline symbol table.

However it does not work correctly. The symbol table doesn't function, can't leverage IC2 features in the module (deploy, run tests etc).

In configure project, I can see the connection and symbol table status look good;

In the toolbar I see IC2 knows the connection based on open file

In my module iml, the IC2 facet, connection info, JDK look correct;

<?xml version="1.0" encoding="UTF-8"?>
<module type="IlluminatedCloud" version="4">
<component name="FacetManager">
<facet type="IlluminatedCloud" name="Illuminated Cloud">
<configuration>
<option name="connectionName" value="TPAY2_main_1009" />
<option name="connectionType" value="SFDX" />
</configuration>
</facet>
</component>
<component name="NewModuleRootManager" inherit-compiler-output="true">
<exclude-output />
<content url="file://$MODULE_DIR$">
<sourceFolder url="file://$MODULE_DIR$/src" isTestSource="false" />
<excludeFolder url="file://$MODULE_DIR$/.sf" />
<excludeFolder url="file://$MODULE_DIR$/.sfdx" />
</content>
<orderEntry type="jdk" jdkName="IlluminatedCloud (monorec/TPAY2_main_1009)" jdkType="IlluminatedCloud" />
<orderEntry type="sourceFolder" forTests="false" />
</component>
</module>

However, the symbol table will not work, and I can not open configure module within the context of the file

So I am not able to deploy on save, or rely on symbol table, or run tests.

Running tests surfaces an interesting error;

Clicking update gives;

A few people on our team have had similar issues and often have to start from scratch with a clean clone of the repo.

I can't see anything off here, and would like to understand the issue without having to start from scratch, or having this impact the team randomly in the future.

Additionally, the project root module is a bare module with not IC2 facet so should not be conflicting facets in the tree;

<?xml version="1.0" encoding="UTF-8"?>
<module version="4">
<component name="NewModuleRootManager" inherit-compiler-output="true">
<exclude-output />
<content url="file://$MODULE_DIR$" />
<orderEntry type="sourceFolder" forTests="false" />
</component>
</module>

And a screenshot of module settings that may be helpful;

Thanks,

Jonny

The information contained herein is confidential and may contain personal or legally privileged information.  It is intended only for the addressee(s).  Any use, distribution or copying of this information by anyone other than the intended recipient is prohibited. If you have received this communication in error, please notify me by e-mail and delete or destroy any copies of this communication.

[Scott]

Jonny, it’s tough to tell what might be going on, but obviously something is amiss as shown in those error messages and the behavior. Do you mind sending over your .idea.log file for review after reproducing those errors? You can email it to me rather than posting it here. Hopefully that’ll show something telling about what might be happening.

Regards,
Scott Wells

​

[Jonny Power (he/him)]

Sure thing - anything you want me to setup (logging flags) or actions to take to trigger specific log entries before sending over?

[Scott]

Let’s just start with a standard log and see what’s in there. Depending on what I see (hopefully something!), I may have you do it again with some specific logging enabled. But for starters I just want to see what kinds of errors are happening. If you don’t mind, please include your project’s .iml file when you send the log over. I know you posted an image of it here, but it’d be useful to be able to look at the exact file as well.

Regards,
Scott Wells

​

[Jonny Power (he/him)]

To loop back here for others - issue is due to overlapping content roots.

We had a root module that has a content root of the root folder, but submodules within that folder can cause conflicts with module ownership of files for IC2. Sometimes it works, sometimes it doesn't - maybe an order of operations or similar.

Anyway, fix is to remove content root on the root module so there isn't conflicting ownership.