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

[web] **ALL** reports shown when the run filter "wildcard pattern" does NOT match ANY runs whatsoever (because typo) #4205

Open
whisperity opened this issue Apr 2, 2024 · 0 comments
Labels
bug 🐛 CLI 💻 Related to the command-line interface, such as the cmd, store, etc. commands web 🌍 Related to the web app

Comments

@whisperity
Copy link
Member

Describe the bug
The web UI returns all the bugs stored in the product when filtering with a run filter that is a wildcard.

CodeChecker version
6.23 release

To Reproduce
Steps to reproduce the behaviour:

https://codechecker-demo.eastus.cloudapp.azure.com/Default/reports?run=*llvm-master-csa&is-unique=off&diff-type=New

  1. I filtered for *llvm-master-csa instead of *llvm-master-version_csa because I misremembered the run name pattern (runs created by the CSA-Testbench).
  2. This run wildcard (the only filter) does NOT match any actual runs.
  3. All 1.85M reports are returned. (It does take a while!)

Expected behaviour
Exactly 0 reports shown (and preferably this result is calculated quickly). The "baseline" runs are a kind of source, if no sources are "allowed" based on the filters, then nothing should come out of the sources.

@whisperity whisperity added bug 🐛 CLI 💻 Related to the command-line interface, such as the cmd, store, etc. commands web 🌍 Related to the web app labels Apr 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug 🐛 CLI 💻 Related to the command-line interface, such as the cmd, store, etc. commands web 🌍 Related to the web app
Projects
None yet
Development

No branches or pull requests

1 participant