[XDP] Fix to manage stream port ID detection in profile for client #8528
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
MCDM build is seeing error with the latest commit to support multi stream IDs.
Bug / issue (if any) fixed, which PR introduced the bug, how it was discovered
(#8509)
How problem was solved, alternative solutions (if any) and why they were rejected
We use equivalent logic in client as well similar to what we have for edge.
startEvent is used to determine portID which further decides on streamPortID to use.
Risks (if any) associated the changes in the commit
Medium- verification is pending on client.
What has been tested and how, request additional testing if necessary
MCDM build is not failing anymore.
Testing of AIE Profile on client is verified with @IshitaGhosh 's help.
Documentation impact (if any)