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

When a new file is opened the CodeChecker analysis should be started in the background #134

Open
dkrupp opened this issue Nov 22, 2023 · 1 comment
Assignees
Labels
bug Something isn't working HIGH
Milestone

Comments

@dkrupp
Copy link
Member

dkrupp commented Nov 22, 2023

When a new source file is opened, the analysis (if not up-to-date) should be automatically executed in the background and the results shouldbe shown in the "reports in current file" tree.

Today, the analysis is not started, only after the "Re-analyze current file" button is pressed.

@dkrupp dkrupp added bug Something isn't working HIGH labels Nov 22, 2023
@dkrupp dkrupp added this to the 1.6 milestone Nov 22, 2023
@dkrupp
Copy link
Member Author

dkrupp commented Nov 24, 2023

We concluded that if we reanalyzed the files always upon file opening that would to too resource consuming.
So instead the vscode plugin should show in the codechecker window that the files "has never been analyzed" or the "analysis is out of date". This needs improvements in CodeChecker see Ericsson/codechecker#4100

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working HIGH
Projects
None yet
Development

No branches or pull requests

2 participants