Skip to content
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

Streamlined logging done by bree jobs. This PR includes logging chang… #964

Merged
merged 1 commit into from
Dec 3, 2024

Conversation

ydahal1
Copy link
Collaborator

@ydahal1 ydahal1 commented Dec 3, 2024

Description

This PR resolves an issue where parallel jobs were independently logging, causing conflicts and occasional loss of logs, by centralizing the logging process so that parallel jobs now send log messages to the parent port or main thread, which handles all logging to ensure conflict-free operation. The fix is applied exclusively to Job Monitoring, while other monitoring components retain the existing logging methodology.

Additionally, the Job Monitoring logic has been updated to address an incorrect assumption that all monitoring systems include ASR-specific metadata, improving compatibility and flexibility.

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Vulnerability fix (package bumps or CodeQL adjustments to ensure code security)
  • This change requires a documentation update

Developer Checklist:

  • I have commented my code, particularly in hard-to-understand areas
  • I have resolved any conflicts with the branch I am attempting to merge to.
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged and published in downstream modules
  • I have checked my code and corrected any misspellings
  • I have ensured that my code does not unecessarily duplicate existing cod
  • I have ensured that all security checks have been passed
  • All input boxes have sensible character limits applied
  • Refreshing related pages puts page in a workable and sensible state

Reviewer Checklist

  • I have pulled the branch into my local environemtn and started the project succesfully
  • I have reviewed the code for proper comments and mispellings
  • All input boxes have sensible character limits applied
  • Refreshing related pages puts page in a workable and sensible state
  • Submitting any relevant Forms relays proper messaging to user
  • I have checked that all security checks have been passed
  • I have checked that all backend routes have proper validation

…es to JM only. Also made adjustment where the JM was assuming all monitoring has ASR releted data
Copy link
Collaborator

@FancMa01 FancMa01 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks Good

@FancMa01 FancMa01 merged commit d2dee56 into dev Dec 3, 2024
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants