-
Notifications
You must be signed in to change notification settings - Fork 3
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
Event filtering gives unexpected exception for inverted fetch time range #76
Comments
This is unrelated to
I believe that it only works for dumps and TSC moves because there is no intersection of the event interval(s) with the fetch data interval. The question is whether to issue an error or warning when a fetch query has effectively invalid inputs, or whether to allow invalid time intervals in remove intervals. Maybe a warning would be useful to discover potential errors in the calling code. In this particular case I would say there is a bug in the upstream code for not checking that the fetch interval is valid. |
When you say "because there is no intersection", which do you mean? |
Comment updated. |
I'm still a little confused about the "fetch data interval". If I had a bad time range for fetch or I have removed intervals so I now have an empty set of times and values, is the "fetch data interval" useful? Also, should a "backwards" fetch range be able to intersect with a valid interval? |
I get an error when trying to remove ltt bads from an empty (inverted range) contained within a day that has an entry in the ltt_bads file. This is obviously a special case, but isn't a problem for the other kadi event intervals.
The text was updated successfully, but these errors were encountered: