Skip to content

Fix FlowView time range overlap filtering - #307

Merged
TheWitness merged 2 commits into
developfrom
fix/flowview-time-range-overlap
Nov 11, 2026
Merged

TheWitness merged 2 commits into
developfrom
fix/flowview-time-range-overlap

Conversation

@somethingwithproof

Copy link
Copy Markdown
Member

Summary

  • Correct the “Any part in specified time span” filter to include flows that overlap the selected range, including flows spanning the entire window.
  • Add regression coverage for the overlap predicate and parameter order.
  • Document the fix in the changelog.

Fixes #306

Validation

  • Focused QueryBuilderTest: 12 tests, 31 assertions.
  • Full Pest suite: 394 tests, 1944 assertions.
  • PHP syntax checks and git diff checks passed.

Signed-off-by: Thomas Vincent <thomasvincent@gmail.com>
The run statistics read map_range_params[0] and [1] as the window start
and end for the shard cache lookup. Binding the overlap predicate as
(end, start) turned that lookup into BETWEEN end AND start, so the
cached size for default-range queries was always 0. Write the overlap
test as end_time >= start AND start_time <= end so the params keep the
same order as every other range type.

Narrow the changelog entry: flows are still read only from the
partitions inside the report window.

Signed-off-by: Thomas Vincent <thomasvincent@gmail.com>
@somethingwithproof
somethingwithproof force-pushed the fix/flowview-time-range-overlap branch from b1b86b3 to 0fa09b2 Compare November 11, 2026 22:59
@sonarqubecloud

Copy link
Copy Markdown

@TheWitness
TheWitness merged commit 295f6eb into develop Nov 11, 2026
7 checks passed
@TheWitness
TheWitness deleted the fix/flowview-time-range-overlap branch November 11, 2026 23:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Include flows spanning the full report time window

2 participants