Load ML Timeline on Client even if other XDP libraries are not available #8792
+33
−27
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
…not available but enabled in runtime config Signed-off-by: Ishita Ghosh <[email protected]>
…ithout returning Signed-off-by: Ishita Ghosh <[email protected]>
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.
Problem solved by the commit
If non-production Client XDP features like AIE Trace/Profile are enabled at runtime but their libraries are not available, then production feature ML Timeline also does not load at runtime. This is fixed in this PR.
Bug / issue (if any) fixed, which PR introduced the bug, how it was discovered
How problem was solved, alternative solutions (if any) and why they were rejected
ML Timeline should get loaded and attached before any other non-production libraries.
Risks (if any) associated the changes in the commit
What has been tested and how, request additional testing if necessary
Unit test on Client Windows
Documentation impact (if any)