sonar-openedge icon indicating copy to clipboard operation
sonar-openedge copied to clipboard

dblist.txt in .sonarlint folder forgets databases

Open dominickdm opened this issue 1 year ago • 4 comments

Hello,

Regarding SonarLint - eclipse plugin: sometimes our .schema files got corrupted, is that a known issue? Every +- 2 weeks I have a colleague with parse errors due to tables that are not found anymore.

SonarLint processing file XXXX Found 0 issue(s) Parser error -- XXX -- Check analysis log for details

The fix is easy, we remove all files in the .SonarLint folder and the files are recreated again when a file is sonar-linted.

Do you see an improvement to either:

  • avoid this issue?
  • automatically reload the schema files after a certain (configurable?) amount of time?
  • automatically reload the schema files when a tables is not found?
  • forsee a menu option to reload the schema files?

dominickdm avatar May 11 '23 10:05 dominickdm

Apologies for the delay. There are no known issues with the .schema files (but clearly doesn't mean it's bug-free). Next time you have an issue, could you send me the content of the .schema file (by email if you don't want it to appear here). I'll have a look at potential causes in the meantime.

gquerret avatar May 29 '23 05:05 gquerret

Hello Gilles, We had the issue again. The schema files are ok, but it seems that the dblist.txt forgot 2 of the 3 databases that are connected.

If needed, I can send you the files.

dominickdm avatar Jun 12 '23 14:06 dominickdm

It is likely to come from a synchronization issue, such as analysis triggered while the AVM session was not connected to all sessions, or one DB was manually disconnected. It's possible to compare the number of DB in the cache to the expected value in the project config, and recreate the cache if the value is different. I'll see if there's some impact. Otherwise, the cache is always recreated every 24 hours.

gquerret avatar Jun 20 '23 14:06 gquerret

FWIW I logged a case that PDSOE should not consider the AVM as started when the databases are not yet connected. It's logged as a defect.

Defect # OCTA-54598 Public Description PDSOE considers AVM start successful when no database is connected

ccecvb avatar Jun 21 '23 10:06 ccecvb