feat(plugin-meetings): chain errors with causes

[Coread]

COMPLETES #< INSERT LINK TO ISSUE >

This pull request addresses

#4260 added the CA error cache. However some errors are thrown that are not also sent in CA events. To address this I've done the following:

1. Add a cause attribute to the AddMediaFailed error.
2. Chain the errors using the cause attribute

This way a client can still inspect the errors to see whether any triggering error in the chain has been sent in a CA event

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.

[coderabbitai]

📝 Walkthrough

Walkthrough

The changes introduce improvements to error handling and propagation within the media connection processes of the Meeting class. The AddMediaFailed error class is updated to accept an optional underlying error as its cause, with a new cause property and an updated constructor. Within the Meeting class, error creation and handling are standardized, with original errors now being included as causes and in metrics reporting. Corresponding unit tests are updated to explicitly check for the new cause property and to ensure that error objects are correctly propagated and included in metrics submissions. No changes are made to public APIs.

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ast-grep (0.31.1)

packages/@webex/plugin-meetings/test/unit/spec/meeting/index.js

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

yarn install v1.22.22
[1/4] Resolving packages...
warning [email protected]: This version is no longer supported. Please see https://eslint.org/version-support for other options.
warning eslint > @humanwhocodes/[email protected]: Use @eslint/config-array instead
warning eslint > @humanwhocodes/config-array > @humanwhocodes/[email protected]: Use @eslint/object-schema instead
warning eslint > file-entry-cache > flat-cache > [email protected]: Rimraf versions prior to v4 are no longer supported
warning eslint > file-entry-cache > flat-cache > rimraf > [email protected]: Glob versions prior to v9 are no longer supported
warning eslint > file-entry-cache > flat-cache > rimraf > glob > [email protected]: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
warning eslint-import-resolver-typescript > [email protected]: Glob versions prior to v9 are no longer supported
warning [email protected]: Glob versions prior to v9 are no longer supported
warning intern > [email protected]: Glob versions prior to v9 are no longer supported
warning intern > glob > [email protected]: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
warning jasmine > [email protected]: Glob versions prior to v9 are no longer supported
warning jest > @jest/core > jest-config > [email protected]: Glob versions prior to v9 are no longer supported
warning jest > @jest/core > jest-runtime > [email protected]: Glob versions prior to v9 are no longer supported
warning jest > @jest/core > @jest/reporters > [email protected]: Glob versions prior to v9 are no longer supported
warning jest > @jest/core > @jest/transform > babel-plugin-istanbul > test-exclude > [email protected]: Glob versions prior to v9 are no longer supported
warning mocha > [email protected]: Glob versions prior to v9 are no longer supported
warning mocha > glob > [email protected]: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
warning [email protected]: 16.1.1
warning sinon > @sinonjs/samsam > [email protected]: This package is deprecated. Use the optional chaining (?.) operator instead.
warning wd > [email protected]: You or someone you depend on is using Q, the JavaScript Promise library that gave JavaScript developers strong feelings about promises. They can almost certainly migrate to the native JavaScript promise now. Thank you literally everyone for joining me in this bet against the odds. Be excellent to each other.

(For a CapTP with native promises, see @endo/eventual-send and @endo/captp)
warning wd > archiver > [email protected]: Glob versions prior to v9 are no longer supported
warning wd > archiver > archiver-utils > [email protected]: Glob versions prior to v9 are no longer supported
warning wd > [email protected]: request has been deprecated, see request/request#3142
warning wd > request > [email protected]: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
warning wd > request > [email protected]: this library is no longer supported
warning @babel/cli > [email protected]: Glob versions prior to v9 are no longer supported
warning @babel/[email protected]: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-async-generator-functions instead.
warning @babel/[email protected]: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-class-properties instead.
warning @babel/[email protected]: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-export-namespace-from instead.
warning @babel/[email protected]: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-nullish-coalescing-operator instead.
warning @babel/[email protected]: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-object-rest-spread instead.
warning @babel/[email protected]: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-optional-chaining instead.
warning @babel/[email protected]: 🚨 This package has been deprecated in favor of separate inclusion of a polyfill and regenerator-runtime (when needed). See the @babel/polyfill docs (https://babeljs.io/docs/en/babel-polyfill) for more information.
warning @babel/polyfill > [email protected]: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.
warning @babel/runtime-corejs2 > [email protected]: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.
warning babel-plugin-lodash > [email protected]: Glob versions prior to v9 are no longer supported
warning workspace-aggregator-9914ddac-490d-4fd2-b568-b35641413c71 > [email protected]: This version is no longer supported. Please see https://eslint.org/version-support for other options.
warning workspace-aggregator-9914ddac-490d-4fd2-b568-b35641413c71 > [email protected]: Glob versions prior to v9 are no longer supported
warning workspace-aggregator-9914ddac-490d-4fd2-b568-b35641413c71 > [email protected]: 16.1.1
warning workspace-aggregator-9914ddac-490d-4fd2-b568-b35641413c71 > @babel/[email protected]: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-async-generator-functions instead.
warning workspace-aggregator-9914ddac-490d-4fd2-b568-b35641413c71 > @babel/[email protected]: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-class-properties instead.
warning workspace-aggregator-9914ddac-490d-4fd2-b568-b35641413c71 > @babel/[email protected]: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-export-namespace-from instead.
warning workspace-aggregator-9914ddac-490d-4fd2-b568-b35641413c71 > @babel/[email protected]: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-nullish-coalescing-operator instead.
warning workspace-aggregator-9914ddac-490d-4fd2-b568-b35641413c71 > @babel/[email protected]: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-object-rest-spread instead.
warning workspace-aggregator-9914ddac-490d-4fd2-b568-b35641413c71 > @babel/[email protected]: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-optional-chaining instead.
warning workspace-aggregator-9914ddac-490d-4fd2-b568-b35641413c71 > @babel/[email protected]: 🚨 This package has been deprecated in favor of separate inclusion of a polyfill and regenerator-runtime (when needed). See the @babel/polyfill docs (https://babeljs.io/docs/en/babel-polyfill) for more information.
[2/4] Fetching packages...
error [email protected]: The engine "node" is incompatible with this module. Expected version "^14 || ^16 || ^17 || ^18 || ^19". Got "22.9.0"
error Found incompatible module.
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

Tip

⚡️ Faster reviews with caching

• CodeRabbit now supports caching for code and dependencies, helping speed up reviews. This means quicker feedback, reduced wait times, and a smoother review experience overall. Cached data is encrypted and stored securely. This feature will be automatically enabled for all accounts on May 16th. To opt out, configure Review - Disable Cache at either the organization or repository level. If you prefer to disable all data retention across your organization, simply turn off the Data Retention setting under your Organization Settings.

Enjoy the performance boost—your workflow just got faster.

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1441cf5 and ce29f82.

📒 Files selected for processing (3)

• packages/@webex/plugin-meetings/src/common/errors/webex-errors.ts (1 hunks)
• packages/@webex/plugin-meetings/src/meeting/index.ts (4 hunks)
• packages/@webex/plugin-meetings/test/unit/spec/meeting/index.js (7 hunks)

🧰 Additional context used

🧬 Code Graph Analysis (3)

packages/@webex/plugin-meetings/src/common/errors/webex-errors.ts (1)

packages/@webex/plugin-meetings/src/common/errors/webex-meetings-error.ts (1)

• WebexMeetingsError (5-35)

packages/@webex/plugin-meetings/test/unit/spec/meeting/index.js (1)

packages/@webex/test-helper-mock-webex/src/index.js (1)

• sinon (12-12)

packages/@webex/plugin-meetings/src/meeting/index.ts (2)

packages/@webex/plugin-meetings/src/meetings/index.ts (1)

• error (81-83)

packages/@webex/plugin-meetings/src/common/errors/webex-errors.ts (1)

• AddMediaFailed (170-170)

⏰ Context from checks skipped due to timeout of 90000ms (2)

• GitHub Check: Initialize Project
• GitHub Check: AWS Amplify Console Web Preview

🔇 Additional comments (12)

packages/@webex/plugin-meetings/src/common/errors/webex-errors.ts (1)

155-168: Well-implemented error chaining support!

The addition of the optional cause property to the AddMediaFailed error class is a good implementation of error chaining. This change aligns with common error handling patterns and will improve debugging capabilities by preserving the original error context.

This implementation will enable the inspection of error chains for Client Analytics events as mentioned in the PR objectives, making it easier to trace error propagation through the system.

packages/@webex/plugin-meetings/src/meeting/index.ts (4)

7162-7163: Improved error reporting in Call Analytics events

The addition of the rawError property to the client event submission enhances error reporting by including the complete error object in the metrics, which will help with diagnostics and debugging.

---

7167-7173: Error chaining implemented to enhance error context

Good implementation of error chaining by creating a new error with a clear message and setting the original error as its cause. This allows consumers to inspect the error chain to get more context about what went wrong.

- const timedOutError = new Error(
-   `Timed out waiting for media connection to be connected, correlationId=${this.correlationId}`
- );
+ const timedOutError = new Error(
+   `Timed out waiting for media connection to be connected, correlationId=${this.correlationId}`
+ );
+ 
+ timedOutError.cause = error;

---

7249-7250: Enhanced error tracking in Client Analytics events

Including the raw error object in the client event submission provides better context for monitoring and debugging, allowing for more effective troubleshooting of media connection issues.

---

7357-7357: Error chaining in AddMediaFailed error

This change implements error chaining for the AddMediaFailed error by passing the original error as a parameter, allowing it to be captured as the cause. This is consistent with the changes in the webex-errors.ts file that added support for the cause attribute to the AddMediaFailed error class.

packages/@webex/plugin-meetings/test/unit/spec/meeting/index.js (7)

2765-2766: Good improvement to error structure in test setup

Creating a specific error object and using it for rejection is a good practice that aligns with the PR objectives. This structured approach enables proper testing of the error chaining feature.

---

2784-2784: Excellent assertion for error chaining

This new assertion correctly verifies that the error's cause property is an instance of Error, which directly validates the error chaining functionality introduced in this PR.

---

2841-2841: Properly passing error to metrics

Good change to include the exact error object in the metrics submission. This ensures full error context is available for analytics, addressing the PR objective of making errors available in CA events.

---

2853-2853: Consistent error inclusion in metrics

Consistently passing the error object as rawError to all relevant metrics submissions maintains proper error propagation throughout the system.

---

2982-2988: Better error creation and propagation

Creating a named error instance with a specific message provides clearer test intentions and allows for better tracking through the error chain. The explicit rejection with this error object improves test quality.

---

3057-3057: Correct propagation of specific error instance

Passing the specific mediaConnectionError instance to metrics submission ensures the exact error that caused the failure is included in analytics, properly implementing the PR objectives.

---

3968-3970: Structured error data in metrics verification

Using a structured object with the iceConnected property provides more detailed error information in metrics, which improves diagnostic capabilities and aligns with the error propagation goals.

✨ Finishing Touches

• 📝 Generate Docstrings

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[aws-amplify-us-east-2]

This pull request is automatically being deployed by Amplify Hosting (learn more).

Access this pull request here: https://pr-4264.d3m3l2kee0btzx.amplifyapp.com