Marco Neumann b12ebe1109 fix: do not panic on invalid timestamp ranges (#5249) ... Timestamp ranges come from "untrusted" inputs (via gRPC) and must not lead to panics. The only case where this could happen is at `start > end`. Let's just set `start = end` in this case. Reaonsing: - Semantically this is a sound range, since this is only a somewhat degenerated case of "empty". - We already allow `start = end` to represent "empty" ranges. - We already clamp (and therefore modify) `start` to the valid range. Fixes https://github.com/influxdata/conductor/issues/1080. Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>		2022-08-01 13:35:34 +00:00
..
src	fix: do not panic on invalid timestamp ranges (#5249)	2022-08-01 13:35:34 +00:00
Cargo.toml	chore(deps): Bump sqlx to 0.6.0 and uuid to 1 (#4894)	2022-06-17 10:28:28 +00:00