This repository was archived by the owner on Sep 12, 2024. It is now read-only.
Removing stdout logging in local logger to avoid runbook getting stuck on write method. #858
Conversation
This file contains hidden or 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
Bug 13865277: [CRI] automationrunbooktracer is hanging in automationrunbooktracer.log() Local logging to stdout is causing write_nocancel method to block indefinitely when there is too much loffing into stdout This logging is only used for debugging purpose, also the logs are getting redirected to runbook* and sandbox* files. Commenting out local stdout logging to resolve this issue.
formatting changes
…/worker Updating agent version to 1.7.10.0 Adding locallogger changes in 3.x/worker
krmanupa
approved these changes
Jun 10, 2022
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
Updating agent version to 1.7.10.0
Adding locallogger changes in 3.x/worker