Add celix err message print in fw after each bundle start #693
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
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## master #693 +/- ##
==========================================
+ Coverage 83.11% 83.42% +0.31%
==========================================
Files 254 254
Lines 32929 32988 +59
==========================================
+ Hits 27369 27521 +152
+ Misses 5560 5467 -93 ☔ View full report in Codecov by Sentry. |
Co-authored-by: PengZheng <howtofly@gmail.com>
…-err-after-bnd-start
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.
This PR add a print of the unprocessed celix err messages after every bundle start.
Ideally errors and therefore celix err messages are handled by the bundle activators, but if this is not done this update will inform users that there are unprocessed celix err messages.