Marek Siarkowicz c37991cf8b Validate watch even if event history cannot be created ...

Creation of event history requires each client to return consistent
events. If clients observed inconsistent view of some revision, merging
will fail and return diff between two clients. This however doesn't
provide hint on what kind of issue happend.

This PR helps cases where there is an error with single watch
stream (like event duplication) by running normal watch validation even
without full event history.

Signed-off-by: Marek Siarkowicz <siarkowicz@google.com>

2024-01-16 16:04:03 +01:00

..

operations.go

Refactor and reorder validation to avoid reporting multiple corelated failures

2023-10-13 14:06:13 +02:00

patch_history_test.go

tests/robustness: Implement loading client reports

2023-06-28 15:35:17 +02:00

patch_history.go

Use the minimal time event was observed on watch

2023-10-13 18:17:29 +02:00

validate_test.go

Refactor and reorder validation to avoid reporting multiple corelated failures

2023-10-13 14:06:13 +02:00

validate.go

Validate watch even if event history cannot be created

2024-01-16 16:04:03 +01:00

watch.go

Validate watch even if event history cannot be created

2024-01-16 16:04:03 +01:00