fix: missing webinar title in OBTP list if another device start webinar#4868
Draft
WeijuanShao wants to merge 2 commits intowebex:nextfrom
Draft
fix: missing webinar title in OBTP list if another device start webinar#4868WeijuanShao wants to merge 2 commits intowebex:nextfrom
WeijuanShao wants to merge 2 commits intowebex:nextfrom
Conversation
|
This pull request is automatically being deployed by Amplify Hosting (learn more). |
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
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.
COMPLETES #< https://jira-eng-gpk2.cisco.com/jira/browse/SPARK-799460 >
This pull request addresses
For this case, we may receive a message that only contains
selfin state_message and is missing the requiredinfoobject. And in creating meeting logic will call the meetingInfo request. We won’t get the correct URI if noinfoobject, which causes the request to fail.Also, when creating a meeting object, it assumes a full locus and initializes certain properties (such as destination) based on it, and these properties won’t be updated later.
In this PR, the change ensures that if the locus is missing
info, we first create a temporary hashTreeParser to construct a complete locus with all necessary data, and then proceed to create the meeting.by making the following changes
< DESCRIBE YOUR CHANGES >
Change Type
The following scenarios were tested
< ENUMERATE TESTS PERFORMED, WHETHER MANUAL OR AUTOMATED >
The GAI Coding Policy And Copyright Annotation Best Practices
I certified that
Make sure to have followed the contributing guidelines before submitting.