-
Notifications
You must be signed in to change notification settings - Fork 21
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
fixes for various null values #613
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You seem to have re-written the whole file. Why?
no, I just changed more of the |
I guess this is the problem. |
@log1-c Can you please reformat your changes and use tabs instead of spaces? go uses tabs. You may use |
done :) |
It looks like this PR includes the changes from #551 (but in new commits) and these changes (only |
I don't see how these additional changes can fix the error stated in #551 (comment):
This PR additionally changes that some columns can read NULL from the IDO database (but then doesn't check for Can you please share a row from the IDO |
Sure. Here are some of the entries where scheduled_end_time is NULL.
|
Interesting, I just ran into the
|
We believe that what you wanted to fix should be fixed by #623. The rows you shared in #613 (comment) all have That fix will be included in Icinga DB 1.1.1 which will be released this week, please report back if you still experience any issues with that version. |
fixes #621
refs #551 (comment)