-
Notifications
You must be signed in to change notification settings - Fork 21
[Availability] Update StatusAggregator to support new AI availability test alerts #778
Conversation
@@ -77,7 +77,11 @@ public IComponent Export() | |||
|
|||
if (currentComponent == null) | |||
{ | |||
throw new InvalidOperationException($"Couldn't find component with path {activeEntity.AffectedComponentPath} corresponding to active entities."); | |||
_logger.LogWarning( |
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.
In the past, all component paths were specified by the job, and if a component path was specified that did not exist, the process would crash.
Because I'm adding an alert that specifies its own component path, I felt it was best to remove this protection. The StatusAggregator job would be essentially permanently stuck if it encountered a malformed AI alert. This way, the process will gracefully ignore any non-existent component paths.
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.
Yeah, good move.
src/StatusAggregator/Parse/AIAvailabilityIncidentRegexParsingHandler.cs
Outdated
Show resolved
Hide resolved
tests/StatusAggregator.Tests/Parse/AIAvailabilityIncidentRegexParsingHandlerTests.cs
Show resolved
Hide resolved
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.
⌚️
[ReleasePrep][2020.05.05] RI of dev into master
[ReleasePrep][2020.05.05] RI of dev into master
https://github.com/nuget/engineering/issues/2581