Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(meetings): add llm plugin as dependency for meetings.min.js #4017

Merged
merged 2 commits into from
Dec 3, 2024

Conversation

sreenara
Copy link
Contributor

@sreenara sreenara commented Dec 3, 2024

COMPLETES # ADOC

This pull request addresses

missing webex.internal.llm plugin within the meetings.min.js
Discussion thread link: webexteams://im?space=2455c470-8b1a-11e6-b5c8-19da9f013fca&message=4f1c7a50-b0aa-11ef-bd02-bf73e4d7a673

by making the following changes

Added @webex/internal-plugin-llm as a dependency for meetings.js

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

Tested the following with https://webex.github.io/webex-js-sdk/samples/browser-plugin-meetings/?meetings

  1. init(), register() with a guest token and check the presence of webex.internal.llm. This object exists now.
  2. Joined a meeting successfully with audio and video. webex.internal.llm.isConnected showed true

meetings-min-js-fix-logs.zip

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.

Summary by CodeRabbit

  • New Features

    • Introduced a new dependency for enhanced functionality with the @webex/internal-plugin-llm.
  • Bug Fixes

    • Maintained existing structure and logic of the Webex initialization process.

@sreenara sreenara added the validated If the pull request is validated for automation. label Dec 3, 2024
@sreenara sreenara requested a review from a team as a code owner December 3, 2024 14:17
Copy link

coderabbitai bot commented Dec 3, 2024

Walkthrough

The changes in this pull request involve the addition of a new dependency, @webex/internal-plugin-llm, in the packages/webex/src/meetings.js file. This addition is made through a new require statement at the beginning of the file. The existing functionality of the Webex.init function remains unchanged, which continues to merge configurations for initializing the Webex instance.

Changes

File Path Change Summary
packages/webex/src/meetings.js Added require('@webex/internal-plugin-llm');

Possibly related PRs

Suggested reviewers

  • marcin-bazyl
  • szotrabh
  • edvujic

🐰 In the meadow, a change did bloom,
A new plugin joined, dispelling the gloom.
Meetings now richer, with features anew,
Webex is hopping, with much more to do!
So let’s gather round, and cheer with delight,
For the code has been spruced, and all feels just right! 🌼

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.

🔧 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.

warning eslint@8.57.1: This version is no longer supported. Please see https://eslint.org/version-support for other options.
warning eslint > @humanwhocodes/config-array@0.13.0: Use @eslint/config-array instead
warning eslint > file-entry-cache > flat-cache > rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
warning eslint > @humanwhocodes/config-array > @humanwhocodes/object-schema@2.0.3: Use @eslint/object-schema instead
warning eslint > file-entry-cache > flat-cache > rimraf > glob@7.2.3: Glob versions prior to v9 are no longer supported
warning eslint > file-entry-cache > flat-cache > rimraf > glob > inflight@1.0.6: 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 > glob@7.2.3: Glob versions prior to v9 are no longer supported
warning glob@7.2.3: Glob versions prior to v9 are no longer supported
warning intern > glob@7.1.7: Glob versions prior to v9 are no longer supported
warning intern > glob > inflight@1.0.6: 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 > glob@7.2.3: Glob versions prior to v9 are no longer supported
warning jest > @jest/core > jest-config > glob@7.2.3: Glob versions prior to v9 are no longer supported
warning jest > @jest/core > jest-runtime > glob@7.2.3: Glob versions prior to v9 are no longer supported
warning jest > @jest/core > @jest/reporters > glob@7.2.3: Glob versions prior to v9 are no longer supported
warning jest > @jest/core > @jest/transform > babel-plugin-istanbul > test-exclude > glob@7.2.3: Glob versions prior to v9 are no longer supported
warning mocha > glob@7.2.0: Glob versions prior to v9 are no longer supported
warning mocha > glob > inflight@1.0.6: 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 sinon@9.2.4: 16.1.1
warning wd > q@1.5.1: 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 > glob@7.2.3: Glob versions prior to v9 are no longer supported
warning wd > request@2.88.0: request has been deprecated, see request/request#3142
warning wd > archiver > archiver-utils > glob@7.2.3: Glob versions prior to v9 are no longer supported
warning wd > request > uuid@3.4.0: 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 > har-validator@5.1.5: this library is no longer supported
warning @babel/cli > glob@7.2.3: Glob versions prior to v9 are no longer supported
warning @babel/plugin-proposal-async-generator-functions@7.20.7: 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/plugin-proposal-class-properties@7.18.6: 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/plugin-proposal-export-namespace-from@7.18.9: 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/plugin-proposal-nullish-coalescing-operator@7.18.6: 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/plugin-proposal-object-rest-spread@7.20.7: 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/plugin-proposal-optional-chaining@7.21.0: 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/polyfill@7.12.1: 🚨 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 > core-js@2.6.12: 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 > core-js@2.6.12: 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 > glob@7.2.3: Glob versions prior to v9 are no longer supported
warning workspace-aggregator-11a68d48-b501-4cd2-9515-d04885d473f8 > eslint@8.57.1: This version is no longer supported. Please see https://eslint.org/version-support for other options.
warning workspace-aggregator-11a68d48-b501-4cd2-9515-d04885d473f8 > glob@7.2.3: Glob versions prior to v9 are no longer supported
warning workspace-aggregator-11a68d48-b501-4cd2-9515-d04885d473f8 > sinon@9.2.4: 16.1.1
warning workspace-aggregator-11a68d48-b501-4cd2-9515-d04885d473f8 > @babel/plugin-proposal-async-generator-functions@7.20.7: 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-11a68d48-b501-4cd2-9515-d04885d473f8 > @babel/plugin-proposal-class-properties@7.18.6: 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-11a68d48-b501-4cd2-9515-d04885d473f8 > @babel/plugin-proposal-export-namespace-from@7.18.9: 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-11a68d48-b501-4cd2-9515-d04885d473f8 > @babel/plugin-proposal-nullish-coalescing-operator@7.18.6: 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-11a68d48-b501-4cd2-9515-d04885d473f8 > @babel/plugin-proposal-object-rest-spread@7.20.7: 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-11a68d48-b501-4cd2-9515-d04885d473f8 > @babel/plugin-proposal-optional-chaining@7.21.0: 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-11a68d48-b501-4cd2-9515-d04885d473f8 > @babel/polyfill@7.12.1: 🚨 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.
error eslint-plugin-jsdoc@40.3.0: The engine "node" is incompatible with this module. Expected version "^14 || ^16 || ^17 || ^18 || ^19". Got "22.9.0"
error Found incompatible module.


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 602e8c6 and a0c7845.

📒 Files selected for processing (1)
  • packages/webex/src/meetings.js (1 hunks)
🔇 Additional comments (3)
packages/webex/src/meetings.js (3)

27-27: LGTM! Verify package availability

The addition of @webex/internal-plugin-llm follows the established pattern for internal plugin imports.

Let's verify the package is properly declared as a dependency:

✅ Verification successful

Dependency and package structure verified

The verification confirms:

  • @webex/internal-plugin-llm is properly declared as a workspace dependency in packages/webex/package.json
  • The package exists at the correct location in the monorepo: packages/@webex/internal-plugin-llm/
🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check if the package is declared as a dependency in package.json
jq -r '.dependencies["@webex/internal-plugin-llm"]' packages/webex/package.json

# Verify the package exists in the monorepo
fd -t d "internal-plugin-llm$" packages/

Length of output: 173


Line range hint 1-47: Verify FedRAMP compliance requirements

Since this change is required for FedRAMP compliance, let's ensure the plugin is properly included in the minified output and meets compliance requirements.

Let's verify the integration:

✅ Verification successful

Based on the gathered information, I can now provide a final response:

FedRAMP configuration is properly integrated and LLM plugin is included in the build

The verification shows:

  • FedRAMP configuration is properly integrated in the core config (@webex/webex-core/src/config.js) with the fedramp flag
  • The LLM plugin is properly included in:
    • The meetings bundle (packages/webex/src/meetings.js)
    • The main webex bundle (packages/webex/src/webex.js)
    • The package list for testing (jest.config.js)
  • FedRAMP tests exist to verify the configuration behavior (packages/webex/test/unit/spec/webex.js)

The integration meets the compliance requirements as it:

  1. Properly loads the LLM plugin
  2. Includes the FedRAMP configuration flag
  3. Has test coverage for FedRAMP-specific behavior
🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check for FedRAMP-related documentation or requirements
rg -i "fedramp" -g "!{*.min.js,*.map}"

# Verify the plugin is included in the build configuration
fd -t f "webpack.config.js$" -x grep -l "internal-plugin-llm" {}

# Look for any FedRAMP compliance tests
rg "fedramp|compliance" -g "*test*"

Length of output: 3109


Script:

#!/bin/bash
# Let's check the webpack configuration files more thoroughly
fd -t f "webpack" -x cat {}

# Check for any LLM plugin configuration in the codebase
rg -A 5 "internal-plugin-llm" --type js

# Check the config files for FedRAMP settings
fd "config.js$" -x cat {}

Length of output: 60832


Line range hint 34-47: Verify LLM plugin configuration requirements

The plugin is loaded but we should verify if it requires any specific configuration in the default config object.

Let's check for any configuration requirements:

✅ Verification successful

No additional LLM configuration required in default config object

The verification shows that:

  1. The LLM plugin is already registered internally with its own configuration
  2. The meetings plugin has enableAutomaticLLM set to false by default in its config
  3. The LLM functionality is properly integrated with the meetings plugin and will be automatically initialized when needed

No additional configuration is required in the default config object as the LLM plugin is properly registered and configured through its own module.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check for any LLM-related configuration in the plugin's source
rg -A 5 "config.*llm" packages/internal-plugin-llm/

# Look for any configuration examples or documentation
fd -t f "README.md$" packages/internal-plugin-llm/ -x cat {}

Length of output: 305


Script:

#!/bin/bash
# Let's first check if the LLM plugin exists in the repository
fd "llm" --type directory

# Search for any LLM-related configuration patterns across the codebase
rg -i "config.*llm|llm.*config" -A 5

# Look for any plugin registration or configuration patterns
ast-grep --pattern 'config = {
  $$$
  llm: $$$
  $$$
}'

Length of output: 73286


Script:

#!/bin/bash
# Let's check for any default configuration in the meetings config
rg -A 5 "config.*meetings" packages/webex/src/

# Search for any LLM-related configuration in the meetings plugin
rg -A 5 "enableAutomaticLLM" packages/@webex/plugin-meetings/src/

# Look for any LLM plugin registration or configuration
rg -A 5 "registerInternalPlugin.*llm" packages/@webex/

Length of output: 2417


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 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.
    • Generate unit testing code for this file.
    • 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 generate unit testing code for this file.
    • @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 generate unit testing code.
    • @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.

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 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.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

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.

@sreenara sreenara enabled auto-merge (squash) December 3, 2024 14:19
Copy link

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

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

@sreenara sreenara merged commit 8225a78 into webex:next Dec 3, 2024
12 of 13 checks passed
@sreenara sreenara deleted the meeting-min-js-llm branch December 3, 2024 15:22
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.

3 participants