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

Gaps reported for epochs,tasks which already have an OK #773

Closed
placer14 opened this issue Nov 23, 2021 · 0 comments · Fixed by #791
Closed

Gaps reported for epochs,tasks which already have an OK #773

placer14 opened this issue Nov 23, 2021 · 0 comments · Fixed by #791
Labels
kind/bug Kind: Bug

Comments

@placer14
Copy link
Contributor

After doing some exploration in our local DB instance, we see many cases where a gap find produces a GAP report for epoch,tasks already have OK processing records. (Specifically, the OK existed and still produced a GAP report after the fact.) Notably, all of these observed rows also contain rows with SKIPs, which may be related.

Here are some records I found in our production DB to illustrate (query at the end): https://gist.github.com/placer14/df45f16be350ae7c3223584fe10a6039

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment