-
Notifications
You must be signed in to change notification settings - Fork 358
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
Alerts style fixes #2047
Merged
Merged
Alerts style fixes #2047
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
ae1b27e
Alerts: split alert_edit.
martinpovolny a95a05e
Alerts: limit branching in alert_edit_save_add.
martinpovolny e739b8d
Alerts: do not call MiqAlert.new or Alert.find 2x.
martinpovolny 05291e0
Alerts: replace find_by_* calls.
martinpovolny a8d0c00
Alerts: decuplicate time hashes.
martinpovolny 517ac5f
Alerts: make Rubocop happy.
martinpovolny File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
This change is breaking the code, since
[:ems_id]
is not guaranteed to be present. So, find raises an exception because is trying to find something withid = 0
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.
more likely there's a null going in and due to the
.to_i
it's converted to the0
Would be nice to know more about the situation and the reasoning so that I could write a test for the regression.
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.
Yes, indeed,
@alert.expression[:options][:ems_id]
is nil, because[:ems_id]
is not set.I cannot speak broadly. At least, for MW-Servers the alerts are not tied to any infrastructure item nor any EMS and this is the reason why there is no
ems_id
in the options hash. The relationship is done through alert profiles.The only kind of alert I could find that asks for a provider is a "VMware Alarm". Probably, this piece of code is specific to those alerts.