Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

dblist.txt in .sonarlint folder forgets databases #1047

Open
dominickdm opened this issue May 11, 2023 · 4 comments
Open

dblist.txt in .sonarlint folder forgets databases #1047

dominickdm opened this issue May 11, 2023 · 4 comments

Comments

@dominickdm
Copy link

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?
@gquerret
Copy link
Contributor

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.

@dominickdm
Copy link
Author

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 dominickdm changed the title .schema files corrupted after some time dblist.txt in .sonarlint folder forgets databases Jun 12, 2023
@gquerret
Copy link
Contributor

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.

@ccecvb
Copy link

ccecvb commented Jun 21, 2023

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants