Skip to content

Fix undefined chat thread in main meeting when breakout room is immediately closed#5640

Merged
mgamis-msft merged 3 commits intomainfrom
mgamis/fix-chat-thread-breakout-room-is-quickly-closed
Feb 11, 2025
Merged

Fix undefined chat thread in main meeting when breakout room is immediately closed#5640
mgamis-msft merged 3 commits intomainfrom
mgamis/fix-chat-thread-breakout-room-is-quickly-closed

Conversation

@mgamis-msft
Copy link
Copy Markdown
Contributor

What

Fix undefined chat thread in main meeting when breakout room is immediately closed.
The chat state in context is set to undefined when joining a breakout room so as to not show the main meeting chat thread.
The chat state will continue to be undefined until the local user is added to the breakout room chat thread. But when the breakout room is closed immediately the chat state will be stuck as undefined. So when the breakout room is closed we should compare the thread id from the chat state context (which is undefined) to the thread id of the origin call chat adapter.

Why

Bug found during bug bash where we see the chat thread is stuck on spinner when immediately returning to main meeting from a closed breakout room.

How Tested

Tested locally

Process & policy checklist

  • I have updated the project documentation to reflect my changes if necessary.
  • I have read the CONTRIBUTING documentation.

Is this a breaking change?

  • This change causes current functionality to break.

@github-actions
Copy link
Copy Markdown
Contributor

Calling bundle size is not changed.

  • Current size: 12401100
  • Base size: 12401100
  • Diff size: 0

@github-actions
Copy link
Copy Markdown
Contributor

CallWithChat bundle size is not changed.

  • Current size: 12401112
  • Base size: 12401112
  • Diff size: 0

@github-actions
Copy link
Copy Markdown
Contributor

Chat bundle size is decreased✅.

  • Current size: 1777255
  • Base size: 1777256
  • Diff size: -1

@github-actions
Copy link
Copy Markdown
Contributor

@github-actions
Copy link
Copy Markdown
Contributor

@azure/communication-react jest test coverage for stable.

Lines Statements Functions Branches
Base 27979 / 44645
62.66%
27979 / 44645
62.66%
786 / 1436
54.73%
2340 / 3713
63.02%
Current 27981 / 44645
62.67%
27981 / 44645
62.67%
786 / 1436
54.73%
2345 / 3715
63.12%
Diff 2 / 0
0.01%
2 / 0
0.01%
0 / 0
0%
5 / 2
0.1%

@github-actions
Copy link
Copy Markdown
Contributor

@azure/communication-react jest test coverage for beta.

Lines Statements Functions Branches
Base 58286 / 94213
61.86%
58286 / 94213
61.86%
1177 / 2694
43.68%
3493 / 5801
60.21%
Current 58348 / 94214
61.93%
58348 / 94214
61.93%
1177 / 2694
43.68%
3577 / 5855
61.09%
Diff 62 / 1
0.07%
62 / 1
0.07%
0 / 0
0%
84 / 54
0.88%

@mgamis-msft mgamis-msft merged commit 78eef1f into main Feb 11, 2025
@mgamis-msft mgamis-msft deleted the mgamis/fix-chat-thread-breakout-room-is-quickly-closed branch February 11, 2025 21:08
mgamis-msft added a commit that referenced this pull request Feb 11, 2025
…iately closed (#5640)

* Fix bug where chat thread is stuck on spinner when breakout room is quickly closed

* Fix code comments

* Change files
@mgamis-msft mgamis-msft mentioned this pull request Feb 11, 2025
3 tasks
mgamis-msft added a commit that referenced this pull request Feb 11, 2025
…iately closed (#5640) (#5642)

* Fix bug where chat thread is stuck on spinner when breakout room is quickly closed

* Fix code comments

* Change files
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants