unexpected interaction of `no_totals=True` with blocking/filtering
Open
Nobody has claimed this yet.
needs: repro
type: bug
- Dominant language
- Python
- Stars
- 15
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
@tzarebczan found a case where no_totals interacts with filtering/blocking by unblocking/unfiltering things.
no_totals=true = shows them
no_totals=true && has_no_source=true doesnt show
default = doesnt show
Ongoing: an example and confirming it affects the latest version
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported combinations of no_totals and has_no_source against the latest version. Trace the filtering and blocking behavior that determines whether results are shown. Done means confirming the example and making the three stated cases behave consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100