Skip to content

fix(plugin-meetings): fix for orphaned meeting#4820

Open
shnaaz wants to merge 1 commit intowebex:nextfrom
shnaaz:shnaaz/fix/SPARK-776971
Open

fix(plugin-meetings): fix for orphaned meeting#4820
shnaaz wants to merge 1 commit intowebex:nextfrom
shnaaz:shnaaz/fix/SPARK-776971

Conversation

@shnaaz
Copy link
Copy Markdown
Contributor

@shnaaz shnaaz commented Mar 30, 2026

COMPLETES #< INSERT LINK TO ISSUE >

https://jira-eng-gpk2.cisco.com/jira/browse/SPARK-776971

This pull request addresses

< DESCRIBE THE CONTEXT OF THE ISSUE >
Only emit MEETING_ADDED if the meeting still exists in the collection.
If fetchMeetingInfo failed and the meeting was destroyed in the catch block,
skip emitting to prevent orphaned meeting references on the consumer side.

by making the following changes

< DESCRIBE YOUR CHANGES >

Change Type

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update
  • Tooling change
  • Internal code refactor

The following scenarios were tested

< ENUMERATE TESTS PERFORMED, WHETHER MANUAL OR AUTOMATED >

The GAI Coding Policy And Copyright Annotation Best Practices

  • GAI was not used (or, no additional notation is required)
  • Code was generated entirely by GAI
  • GAI was used to create a draft that was subsequently customized or modified
  • Coder created a draft manually that was non-substantively modified by GAI (e.g., refactoring was performed by GAI on manually written code)
  • Tool used for AI assistance (GitHub Copilot / Other - specify)
    • Github Copilot
    • Other - Please Specify
  • This PR is related to
    • Feature
    • Defect fix
    • Tech Debt
    • Automation

I certified that

  • I have read and followed contributing guidelines
  • I discussed changes with code owners prior to submitting this pull request
  • I have not skipped any automated checks
  • All existing and new tests passed
  • I have updated the documentation accordingly

Make sure to have followed the contributing guidelines before submitting.

@shnaaz shnaaz requested review from a team as code owners March 30, 2026 13:18
@shnaaz shnaaz added the validated If the pull request is validated for automation. label Mar 30, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

validated If the pull request is validated for automation.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants