- edited description
- attached Logs.png
- attached Application_Config.png
Cmd+S is not triggering deployment
Suddenly the deploy on save stopped working today. I am not sure what am I missing?
Webstrom version: 2024.2. Build: #WS-242.20224.342
I have added all the relevant details below.
Log Level Config
com.illuminatedcloud.intellij.builder.IlluminatedCloudDeployOnSaveAllActionListener
com.illuminatedcloud.intellij.builder.IlluminatedCloudSaveAllAction
com.illuminatedcloud.intellij.builder.ForceComBuilder
com.illuminatedcloud.intellij.builder.ForceComBuilderUtil
com.illuminatedcloud.intellij.builder.ForceComMetadataApiDeployer
com.illuminatedcloud.intellij.builder.ForceComSfdxMetadataDeployer
com.illuminatedcloud.intellij.builder.ForceComSfdxDeployer
com.illuminatedcloud.intellij.builder.ForceComSfdxMetadataUtil
com.illuminatedcloud.intellij.builder.ForceComToolingApiDeployer
com.illuminatedcloud.intellij.builder.ForceComBuildFailureAnnotator
com.illuminatedcloud.util.VariableLengthPollingInterval
Comments (13)
-
reporter -
reporter - marked as major
-
repo owner - changed status to open
Hi. Can you please attach or email the entire
idea.log
file for review so that I can see the full deployment attempt? Also, can you confirm that the file(s) you're trying to deploy are under a configured source root?I've just tried to reproduce this in a metadata format project, a source format project not against a source-tracked org, and a source format project against a source-tracked/scratch org, and in all cases Ctrl+S is triggering the appropriate type of deployment. Hopefully what you're seeing is just some kind of configuration issue. I also confirmed the correct behavior on a Mac using Cmd+S.
-
reporter - attached idea.log
-
reporter Hello,
Yeah the files are under a configured source root. It was working as expected previously but it started breaking suddenly after I performed few git operations (not at all related to IC2 itself).
I updated the sf, webstorm and reinstalled the IC2 after that, since I wasn’t able to figure out what went wrong. -
repo owner Thank you for the log. I’m a little confused as to what I’m seeing, though. I do see the following a few times:
2024-08-15 20:37:58,879 [37072831] INFO - #com.illuminatedcloud.intellij.builder.deploy.IlluminatedCloudDeployOnSaveAllActionListener - The system Save All action was invoked for project <projectName>.
However, I’d expect to see one of the following three messages immediately after that:
Project features are disabled.
Deploy-on-save is disabled.
Determining which files should be included in the deploy-on-save operation.
However, I’m not seeing any of those. They’re all logged at the debug level, but I can see where those are properly configured for debug logging in your log:
2024-08-15 18:28:53,227 [ 338508] INFO - #c.i.d.l.LogLevelConfigurationManager - Level DEBUG is set for the following category: #com.illuminatedcloud.intellij.builder.IlluminatedCloudDeployOnSaveAllActionListener 2024-08-15 18:28:53,227 [ 338508] INFO - #c.i.d.l.LogLevelConfigurationManager - Level DEBUG is set for the following category: com.illuminatedcloud.intellij.builder.IlluminatedCloudDeployOnSaveAllActionListener
Did you by chance upgrade this WebStorm installation to 2024.2 in-place? I ask because I’ve now helped two people with strange issues that were completely resolved by uninstalling and then reinstalling the JetBrains IDE after one or more in-place upgrades. Given that this also seems to be an odd behavior where it’s either not reaching expected logic or isn’t logging what it’s doing in a useful manner, it may be worth doing that real quick. You won’t lose any of your settings.
-
repo owner For reference, here’s what I see in my
idea.log
when I deploy a file via Ctrl+S:2024-08-15 20:37:58,879 [37072831] INFO - #com.illuminatedcloud.intellij.builder.deploy.IlluminatedCloudDeployOnSaveAllActionListener - The system Save All action was invoked for project df17-with-manifest. 2024-08-15 20:37:58,879 [37072831] FINE - #com.illuminatedcloud.intellij.builder.deploy.IlluminatedCloudDeployOnSaveAllActionListener - Determining which files should be included in the deploy-on-save operation. 2024-08-15 20:37:58,879 [37072831] FINE - #com.illuminatedcloud.intellij.builder.deploy.IlluminatedCloudDeployOnSaveAllActionListener - Adding files from the event data context. 2024-08-15 20:37:58,880 [37072832] FINE - #com.illuminatedcloud.intellij.builder.deploy.IlluminatedCloudDeployOnSaveAllActionListener - Finding builder for file C:/Users/Scott/dev/projects/IlluminatedCloudTestProjects/df17-with-manifest/force-app/main/default/classes/MultiMap.cls. 2024-08-15 20:37:58,880 [37072832] FINE - #com.illuminatedcloud.intellij.builder.deploy.IlluminatedCloudDeployOnSaveAllActionListener - Using builder for connection demo. 2024-08-15 20:37:58,880 [37072832] FINE - #com.illuminatedcloud.intellij.builder.deploy.IlluminatedCloudDeployOnSaveAllActionListener - Adding unsaved files from tabbed editors. 2024-08-15 20:37:58,880 [37072832] FINE - #com.illuminatedcloud.intellij.builder.deploy.IlluminatedCloudDeployOnSaveAllActionListener - Seeing if C:/Users/Scott/dev/projects/IlluminatedCloudTestProjects/df17-with-manifest/force-app/main/default/classes/MultiMap.cls is in a tabbed editor with other unsaved files. 2024-08-15 20:37:58,884 [37072836] FINE - #com.illuminatedcloud.intellij.builder.deploy.IlluminatedCloudDeployOnSaveAllActionListener - Adding explicitly-selected files. 2024-08-15 20:37:58,884 [37072836] FINE - #com.illuminatedcloud.intellij.builder.deploy.IlluminatedCloudDeployOnSaveAllActionListener - Found 1 file(s) explicitly requested for deploy-on-save. 2024-08-15 20:37:58,884 [37072836] FINE - #com.illuminatedcloud.intellij.builder.deploy.IlluminatedCloudDeployOnSaveAllActionListener - Adding modified source files. 2024-08-15 20:37:58,884 [37072836] FINE - #com.illuminatedcloud.intellij.builder.deploy.IlluminatedCloudDeployOnSaveAllActionListener - No additional modified files were found. 2024-08-15 20:37:58,885 [37072837] FINE - #com.illuminatedcloud.intellij.builder.deploy.IlluminatedCloudDeployOnSaveAllActionListener - Deploying 1 files to connection demo.
Here’s what I see if I type Ctrl+S while deploy-on-save is disabled:
2024-08-15 21:10:37,557 [39031509] INFO - #com.illuminatedcloud.intellij.builder.deploy.IlluminatedCloudDeployOnSaveAllActionListener - The system Save All action was invoked for project df17-with-manifest. 2024-08-15 21:10:37,557 [39031509] FINE - #com.illuminatedcloud.intellij.builder.deploy.IlluminatedCloudDeployOnSaveAllActionListener - Deploy-on-save is disabled. 2024-08-15 21:10:37,560 [39031512] FINE - #com.illuminatedcloud.intellij.builder.deploy.IlluminatedCloudDeployOnSaveAllActionListener - Deploy-on-save is disabled.
And finally here’s what I see if I type Ctrl+S while the entire license is disabled:
2024-08-15 21:12:07,102 [39121054] INFO - #com.illuminatedcloud.intellij.builder.deploy.IlluminatedCloudDeployOnSaveAllActionListener - The system Save All action was invoked for project df17-with-manifest. 2024-08-15 21:12:07,102 [39121054] FINE - #com.illuminatedcloud.intellij.builder.deploy.IlluminatedCloudDeployOnSaveAllActionListener - Product features are disabled. 2024-08-15 21:12:07,105 [39121057] FINE - #com.illuminatedcloud.intellij.builder.deploy.IlluminatedCloudDeployOnSaveAllActionListener - Product features are disabled.
I would expect at least one of those to be logged when debug logging is enabled, but yours just stops after the first line from each.
-
reporter I downloaded the latest version and replaced the application and definitely didn’t clear any
~/Library/caches/...
or any otherApplication Support
.
But I did that because I ran into this issue. -
repo owner Oh, wait. Please update your debug logging based on what’s here:
https://www.illuminatedcloud.com/support/debug-logging
Yours is:
com.illuminatedcloud.intellij.builder.IlluminatedCloudDeployOnSaveAllActionListener com.illuminatedcloud.intellij.builder.IlluminatedCloudSaveAllAction com.illuminatedcloud.intellij.builder.ForceComBuilder com.illuminatedcloud.intellij.builder.ForceComBuilderUtil com.illuminatedcloud.intellij.builder.ForceComMetadataApiDeployer com.illuminatedcloud.intellij.builder.ForceComSfdxMetadataDeployer com.illuminatedcloud.intellij.builder.ForceComSfdxDeployer com.illuminatedcloud.intellij.builder.ForceComSfdxMetadataUtil com.illuminatedcloud.intellij.builder.ForceComToolingApiDeployer com.illuminatedcloud.intellij.builder.ForceComBuildFailureAnnotator com.illuminatedcloud.util.VariableLengthPollingInterval
but it should be:
com.illuminatedcloud.intellij.builder.annotator.ForceComBuildFailureAnnotator com.illuminatedcloud.intellij.builder.deploy.action.IlluminatedCloudSaveAllAction com.illuminatedcloud.intellij.builder.deploy.ForceComMetadataApiDeployer com.illuminatedcloud.intellij.builder.deploy.ForceComSfDeployer com.illuminatedcloud.intellij.builder.deploy.ForceComSfPushDeployer com.illuminatedcloud.intellij.builder.deploy.ForceComToolingApiDeployer com.illuminatedcloud.intellij.builder.deploy.IlluminatedCloudDeployOnSaveAllActionListener com.illuminatedcloud.intellij.builder.ForceComBuilder com.illuminatedcloud.intellij.builder.IlluminatedCloudFileHandler com.illuminatedcloud.intellij.builder.refactoring.move.IlluminatedCloudMoveFileHandler com.illuminatedcloud.intellij.builder.util.ForceComBuilderUtil com.illuminatedcloud.intellij.builder.validate.AsYouTypeEventProcessor com.illuminatedcloud.intellij.lightning.util.LightningDeployResult com.illuminatedcloud.intellij.util.VariableLengthPollingInterval
Notice the slight change in packaging resulting from a set of changes about 6 months ago, e.g.,
builder.deploy
instead ofbuilder
.Please update that, reproduce the behavior, and provide a new
idea.log
for review. -
reporter So I just updated the log config as you suggested above and it started working again.
Deployments are happening seamlessly again.I have no clue why this config change fixed it and why did it stopped working in the first place?
But thanks a lot Scott for all the help and support. -
repo owner That is bizarre. Does it stop working if you remove that debug logging? Probably not. Either way, please let me know if you ever see this again and we’ll take another close look at it.
-
repo owner - changed status to resolved
It seems that just "jiggling the wires" put things right again...
-
reporter Hahah..
Definitely seems that way and also I restarted my machine couple of times through this whole figuring out process, the oldest trick in the hat.
Nopes, removed the logging and tested, it still works. - Log in to comment