Problems tab does not refresh when issues are addressed #2608

robcowell · 2020-10-08T07:24:03Z

Summary

Problems tab in VS code reports issues that have since been addressed and only restarting VS Code clears them down

Steps To Reproduce:

Create some Apex code with issues ¯_(ツ)_/¯
Fix the issues
Save the code

Expected result

Problems list should clear down.

Actual result

Problems list persists with those issues, file remains highlighted in sidebar (red in my theme).

Additional information

See screenshot.

VS Code Version: 1.49.3

SFDX CLI Version: 7.75.0-5521f40d11 Win32-x64 node-v12.18.3

OS and version: Windows Server 2012 R2 Standard (but also seen on my local machine Win10 Pro)

BrettMN · 2020-10-08T15:59:24Z

I have the same... Problems

VS Code Version: 1.50.0-insider

SFDX CLI Version: sfdx-cli/7.75.0 darwin-x64 node-v12.18.4

OS and version: MacOS Catalina 10.15.7

RPDevJesco · 2020-10-08T16:13:27Z

During those situations, reloading VS Code should fix the issue. Has something to do with the VSCode cache.

BrettMN · 2020-10-08T16:45:10Z

That workaround would mean restarting VS Code ever couple of minutes.

I'd end up spending more time waiting for things to save, not refresh the problems and re-opening VSCode than doing work.

This is only happening in an SFDX Project for me as well. Other projects, where the SFDX plugins are disabled, do not have this issue.

lcampos · 2020-10-09T21:24:41Z

Hi thanks for opening this issue. Can you confirm if these lines in the Problems tab are a result of a failed deploy (specific to Apex code) ? If they are then this is working as designed since the list of errors is kept around until the next time a deploy happens. That is because it's currently not possible to evaluate if the error was actually fixed without re-deploying.

robcowell · 2020-10-09T21:27:51Z

I have the deploy on save feature enables so no, a subsequent deploy doesn't clear them down. Not sure if the beta quick deploy feature is a factor here, I use that.

…

On 9 October 2020 22:25:03 lcampos ***@***.***> wrote: Hi thanks for opening this issue. Can you confirm if these lines in the Problems tab are a result of a failed deploy ? If they are then this is working as designed since the list of errors is kept around until the next time a deploy happens. That is because it's currently not possible to evaluate if the error was actually fixed without re-deploying. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

KoninosV2 · 2020-10-13T08:20:20Z

For me, the procedure to recreate the problem is:

Write code with problems (that don't get picked up on save but on deploy e.g. wrong sobject name).
Save the file
Try to deploy the file (and fail)
3.1. Now the problems get the red underline and shown in the Problems tab.
Fix the problems.
Save the file.

This way I can reproduce the bug every time. Enabling/Disabling the experimental Retrieve-Deploy doesn't impact this.
The problems stick around even after a successful deploy, resulting in them adding up and making the file filled with red lines and underlining.

pogilvieCB · 2020-10-23T14:29:55Z

I have the same problem when executing anonymous apex. Could we have a switch to turn off problem highlighting until this is fixed? I'm kind of OCD so it's making vscode almost unusable.

lcampos · 2020-10-29T18:41:16Z

Closing this since the fix was released in version 50.3.0 of the Salesforce extensions for VSCode. Thanks for providing feedback.

AndrewStopchenko-SO · 2023-06-07T16:21:26Z

Hi, I am experiencing this same issue again.

Steps To Reproduce:

Create new Project With Manifest (Empty template), create a scratch org.
Create Test1 Apex class with code below and try pushing the source to default org:
Result - push fails, "Illegal assignment from String to Decimal" problem gets added to the "Problems" panel.

public with sharing class Test1 {
    public static void foo() {
        Decimal i = '42';
        System.debug('i = ' + i);
    }
}

Run "SFDX: Push Source to Default Org" command several more times.
Result - the problem gets added to the "Problems" panel multiple times:
Update the Test1 class to fix the problematic assignment as Decimal i = 42;, and push the source to default org again:
Result - push succeeds, but the problems from 3 Result are not removed from the "Problems" panel.

Workarounds?

Restarting the VSCode's Extensions Host cleans up the "Problems" panel.
Restart VSCode also cleans up the "Problems" panel.
UPDATE: reverting Salesforce CLI Integration extension to v57.15.0 solved the problem for me. Guess: this might be related to/caused by fix: Make Push and Pull Update Cache to Work with VSCE Conflict Detection #4853.

Additional information

VSCode version: 1.78.2
OS: Windows_NT x64 10.0.19044
Salesforce Extension Pack extension version: 58.0.1

SFDX CLI details:

sfdx-cli/7.203.6 win32-x64 node-v18.15.0
@oclif/plugin-autocomplete 2.2.0 (core)
@oclif/plugin-commands 2.2.15 (core)
@oclif/plugin-help 5.2.9 (core)
@oclif/plugin-not-found 2.3.23 (core)
@oclif/plugin-plugins 3.1.0 (core)
@oclif/plugin-search 0.0.17 (core)
@oclif/plugin-update 3.1.15 (core)
@oclif/plugin-version 1.3.4 (core)
@oclif/plugin-warn-if-update-available 2.0.37 (core)
@oclif/plugin-which 2.2.21 (core)
@salesforce/sfdx-scanner 3.12.0 (latest-pilot)
apex 2.2.21 (core)
auth 2.7.16 (core)
community 2.2.12 (core)
custom-metadata 2.1.22 (core)
data 2.3.19 (core)
deploy-retrieve 1.10.1 (core)
info 2.6.14 (core)
limits 2.3.17 (core)
org 2.9.1 (core)
packaging 1.17.1 (core)
schema 2.3.10 (core)
settings 1.4.9 (core)
sfdx-cli 7.203.6 (core)
signups 1.4.19 (core)
sobject 0.1.22 (0.1.8)
source 2.10.10 (core)
telemetry 2.2.0 (core)
templates 55.4.17 (core)
trust 2.4.19 (core)
user 2.3.14 (core)

vnehess · 2023-06-08T15:44:42Z

I am observing this issue again, today. as described above by AndrewStopchenko-SO

lockholster · 2023-06-09T02:56:29Z

Thanks @AndrewStopchenko-SO, I'd say you're correct here in your update:

reverting Salesforce CLI Integration extension to v57.15.0 solved the problem for me. Guess: this might be related to/caused by #4853.

I've been experiencing the same issue, and reverting the CLI integration to 57.15 worked for me too.

simonhyphen8 · 2023-06-09T10:21:43Z

I am seeing this issue today as reported by @AndrewStopchenko-SO
Can someone confirm if the only solution is to revert the CLI integration to 57.15? Or is there a fix due? Thanks.

kkoellner · 2023-06-09T17:45:49Z

Also having the issue today. Totally pain as you can click on a Problem in the Problem pain to jump to the line of code but not in the Output pain. But, I'm having to wade through things I fixed an hour ago.

ccalvomartinez · 2023-06-12T08:44:51Z

@AndrewStopchenko-SO

This worked for me:

UPDATE: reverting Salesforce CLI Integration extension to v57.15.0 solved the problem for me. Guess: this might be related to/caused by #4853.

Thank you very much for the solution. This issue was driving me crazy.

ram4ufriends · 2023-06-12T15:55:32Z

Happening again. Not sure why this is getting repeated after every few releases..

willvoyle · 2023-06-13T10:17:23Z

Also, getting the same issue. Very inefficient, restarting VS code every time.

simonhyphen8 · 2023-06-13T10:19:27Z

@ram4ufriends @willvoyle
Downgrading the CLI Plugin to V57.15 did work for me, but downgrading to an earlier version of the plugin doesn't seem like the best fix. Hopefully this will be fixed and we can use the most recent version of the CLI plugin.

willvoyle · 2023-06-13T10:22:46Z

@simonhyphen8 It also worked for me, the exact name of the extension is "Salesforce CLI Integration". Steps are below:

Open VS Code
Extensions Tab
Search for 'Salesforce CLI Integration'
Click down arrow next to 'Uninstall'
Click 'Install Another Version...'
Select '57.15'
Reload VS Code

theperiscope · 2023-06-15T14:04:23Z

@simonhyphen8 Happens for me as well with latest 58.2.0 extension packversion. The workaround for this issue worked.

genpact-dev-kuldeep · 2023-06-22T06:01:34Z

Ideally it should not break in latest release. Can someone fix this. This is a MAJOR BUG and it is hampering development directly. It is perfect in V 57.15 and i am working in lower version. Any one having update to current version - 58.3.1? as of today.

lucas7005 · 2023-06-22T09:28:41Z

I have updated to v58.3.1 and this issue is still happening.

AndrewStopchenko-SO · 2023-06-22T11:45:04Z

It doesn't look like this closed issue is reviewed by the project's team.

There was a new issue #4904 tracked for similar problem - so, we should probably keep an eye on that open issue instead.

GerbenRampaart · 2024-05-16T08:15:49Z

This is such a long running problem, that version after version still exists.

lcampos added the more information required label Oct 9, 2020

no-response bot removed the more information required label Oct 9, 2020

This was referenced Oct 26, 2020

fix: clear deploy diagnostics #2671

Merged

SFDX does not clear Problems panel after fixing errors and submit again #2645

Closed

brpowell mentioned this issue Oct 27, 2020

fix: diagnostics not clearing for apex execute #2673

Merged

lcampos closed this as completed Oct 29, 2020

robcowell mentioned this issue Oct 30, 2020

Anon Apex under VS Code not clearing error cache #2689

Closed

This was referenced Jun 8, 2023

Problems Flagged in Problems Tab Persist After Successful Deployment #4915

Closed

Issue on problem panel not get clear after successful deployment #4904

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Problems tab does not refresh when issues are addressed #2608

Problems tab does not refresh when issues are addressed #2608

robcowell commented Oct 8, 2020

BrettMN commented Oct 8, 2020

RPDevJesco commented Oct 8, 2020

BrettMN commented Oct 8, 2020

lcampos commented Oct 9, 2020 •

edited

robcowell commented Oct 9, 2020 via email

KoninosV2 commented Oct 13, 2020

pogilvieCB commented Oct 23, 2020

lcampos commented Oct 29, 2020

AndrewStopchenko-SO commented Jun 7, 2023 •

edited

vnehess commented Jun 8, 2023

lockholster commented Jun 9, 2023

simonhyphen8 commented Jun 9, 2023

kkoellner commented Jun 9, 2023

ccalvomartinez commented Jun 12, 2023

ram4ufriends commented Jun 12, 2023

willvoyle commented Jun 13, 2023

simonhyphen8 commented Jun 13, 2023

willvoyle commented Jun 13, 2023 •

edited

theperiscope commented Jun 15, 2023

genpact-dev-kuldeep commented Jun 22, 2023

lucas7005 commented Jun 22, 2023

AndrewStopchenko-SO commented Jun 22, 2023

GerbenRampaart commented May 16, 2024

Problems tab does not refresh when issues are addressed #2608

Problems tab does not refresh when issues are addressed #2608

Comments

robcowell commented Oct 8, 2020

Summary

Steps To Reproduce:

Expected result

Actual result

Additional information

BrettMN commented Oct 8, 2020

RPDevJesco commented Oct 8, 2020

BrettMN commented Oct 8, 2020

lcampos commented Oct 9, 2020 • edited

robcowell commented Oct 9, 2020 via email

KoninosV2 commented Oct 13, 2020

pogilvieCB commented Oct 23, 2020

lcampos commented Oct 29, 2020

AndrewStopchenko-SO commented Jun 7, 2023 • edited

Steps To Reproduce:

Workarounds?

Additional information

vnehess commented Jun 8, 2023

lockholster commented Jun 9, 2023

simonhyphen8 commented Jun 9, 2023

kkoellner commented Jun 9, 2023

ccalvomartinez commented Jun 12, 2023

ram4ufriends commented Jun 12, 2023

willvoyle commented Jun 13, 2023

simonhyphen8 commented Jun 13, 2023

willvoyle commented Jun 13, 2023 • edited

theperiscope commented Jun 15, 2023

genpact-dev-kuldeep commented Jun 22, 2023

lucas7005 commented Jun 22, 2023

AndrewStopchenko-SO commented Jun 22, 2023

GerbenRampaart commented May 16, 2024

lcampos commented Oct 9, 2020 •

edited

AndrewStopchenko-SO commented Jun 7, 2023 •

edited

willvoyle commented Jun 13, 2023 •

edited