-
Notifications
You must be signed in to change notification settings - Fork 14
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
#4079 - Queue Monitoring - Schedulers Refactor (Part 7) #4179
#4079 - Queue Monitoring - Schedulers Refactor (Part 7) #4179
Conversation
this.logger.log("ECE request file generation completed."); | ||
|
||
if (!uploadResults.length) { | ||
return "No eligible COEs found."; |
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.
👍
const locationResultSummary = new ProcessSummary(); | ||
processSummary.children(locationResultSummary); | ||
result.summary.forEach((info) => locationResultSummary.info(info)); | ||
result.warnings.forEach((error) => locationResultSummary.warn(error)); | ||
result.errors.forEach((error) => locationResultSummary.error(error)); |
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.
Is there a particular reason why we did not use the process summary inside the processing service here?
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.
The service is heavily relying in the current summary and replacing it by the ProcessSummary
would demand way more refactor, which I considered completely outside the target of this effort.
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.
Makes sense. Can we have a ticket created to not lose the track of that effort?
...ocessors/schedulers/institution-integration/ier12-integration/ier12-integration.scheduler.ts
Show resolved
Hide resolved
...ocessors/schedulers/institution-integration/ier12-integration/ier12-integration.scheduler.ts
Outdated
Show resolved
Hide resolved
} catch (error: unknown) { | ||
const errorMessage = "Error while uploading content for IER 12."; | ||
this.logger.error(errorMessage, error); | ||
processSummary.error(errorMessage, error); |
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.
What could be the benefit of not throwing the error here?
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.
First, the previous log that stated "processing must continue for the next institution without aborting." was misleading because this block is the last one before wrapping up the operation.
Throwing or not throwing here will not change the fact that the job will retry, but not throwing will allow the IER12UploadResult
to be returned and logged before the job fails.
Good Job @andrewsignori-aot. Only minor comments. |
|
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.
Thanks for making the changes. Looks good. 👍
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.
LGTM, nice work @andrewsignori-aot
Refactored the below schedulers and E2E tests.