Problem view not populated after compiling

[Max-crosskey]

I seem to encounter an issue every now and then where the problems view doesn't get populated with errors after failed compile. It seems to mostly happen in instances where a semicolon is missing or similar things. I usually have to compile through RDi to find those problems.

[AbhishekSingh888]

Could you please try the following once and let us know the outcome?
After making a small change in the source, please wait a few seconds to ensure the source is fully saved on IBM i before triggering the compile. Then run the compile and check whether the Problems view is populated correctly if the compile fails.

This will help us verify whether the issue is related to the source not being fully saved before the compile is initiated.

Thankyou

[Max-crosskey]

Hi,
This seemed to work for some of the times this happens but now I can replicate it again and most of the time the problems view is empty and sometimes I only get this :
Compile component X to update ARCAD-Observer codelenses

While compiling in RDi tells me that
RNF7535 The type and attributes of parameter 1 do not match those of the prototype.

In VSC I've tried closing source and compiling, making dummy change and waiting several seconds before compiling but hasn't worked

[AbhishekSingh888]

I have addressed the latency issue between saving the file and compiling it in ARCAD. However, I was not able to reproduce the issue you mentioned. Could you please share the version of Elias you currently have installed?

[Max-crosskey]

Now I can replicate this issue by just writing the name of the variable and nothing else:

The extension version is 2.5.3

[Max-crosskey]

Yesterday I noticed same issue when the error I should have gotten is 'Definition not found for symbol X' which was due to my serviceprogram I was using wasn't compiled. The problem view was empty.

[AbhishekSingh888]

Thanks @Max-crosskey, I will try to recreate the scenario and will keep you updated as soon as I find a fix.

[Max-crosskey]

I don't know if this is related but I also encounter issues where old sources stay in the Problems view:

Those have been closed and compiled succesfully earlier in the day. And the one with 46 errors is a duplicate for same component

[Max-crosskey]

Also encountered this now when I had changed the name of an external procedure in program Y, and then when I tried to recompile program X that used the old name for the procedure then the compile failed but didn't give any errors

[AbhishekSingh888]

Hi @Max-crosskey , apologies for the delay due to other work. The issue is most likely related to cached data not being cleared. I'll try to replicate the scenario and update you soon.

[Max-crosskey]

Hi again, I have noticed that when I get this issue the problems view flashes briefly with the errors for a second and then it disappears. So it does get populated but gets cleared immediately?