Improve 'MarathonEvent' & Marathon event handler's log #113
Conversation
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
hyper0x
force-pushed
the
master
branch
2 times, most recently
from
931bca1
to
cea42f2
Compare
Closed
|
I would strongly suggest that Bamboo uses a ADVANCED logging library. |
|
@activars Please review this. And, I found a hidden danger in services/event_handler.go. I will fix it. |
Merge from original repo
|
Cleaning up PRs. Feel free to reopen if still relevant. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I think it is not enough to understanding the marathon events via the log. So I improved it.