use uuid for LlamaCloud in e2e test

[leehuwuj]

Summary by CodeRabbit

• New Features

  • Enhanced end-to-end testing capabilities with the addition of the --llamacloud datasource option.

• Bug Fixes

  • Improved logging during index creation for better debugging and monitoring.

• Chores

  • Updated dependencies for llama-index-express-streaming and llama-index-nextjs-streaming projects to the latest version.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 0a4dda4

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The pull request includes modifications to the GitHub Actions workflow for end-to-end (E2E) tests, specifically adding a new datasource option for the e2e-typescript job. Additionally, the loadAndIndex function in the generate.ts file has been updated to enable verbose logging during index creation. Furthermore, the package.json files for two streaming projects have been updated to reflect a version bump in the llamaindex dependency.

Changes

File Path	Change Summary
.github/workflows/e2e.yml	Updated datasources in e2e-typescript job to include "--llamacloud" alongside existing options.
templates/components/vectordbs/typescript/llamacloud/generate.ts	Modified loadAndIndex to include { verbose: true } in the call to index.ensureIndex().
templates/types/streaming/express/package.json	Updated llamaindex dependency version from 0.6.21 to 0.6.22.
templates/types/streaming/nextjs/package.json	Updated llamaindex dependency version from 0.6.21 to 0.6.22.

Possibly related PRs

• feat: add e2e testing for llamacloud datasource #181: This PR adds end-to-end testing for the LlamaCloud datasource, which is directly related to the changes in the main PR that also involve modifications to the E2E workflow for LlamaCloud.
• refactor: test frameworks via matrix #211: This PR modifies the .github/workflows/e2e.yml file to enhance the testing framework, which aligns with the changes made in the main PR regarding the E2E workflow configuration.
• refactor: e2e tests #256: This PR reflects significant modifications to the E2E workflow configuration, similar to the changes made in the main PR, indicating a focus on improving the testing process.
• feat: add test and fix python dependencies #304: This PR introduces tests related to Python dependencies, which may interact with the E2E testing framework mentioned in the main PR.
• reorganize e2e tests (split Python and TS) #329: This PR reorganizes the E2E tests by splitting them into Python and TypeScript categories, which is relevant to the overall structure and organization of the E2E testing framework discussed in the main PR.

Suggested reviewers

• thucpn

Poem

🐇 In the meadow where we play,
New tests bloom, bright as day.
With LlamaCloud now in sight,
Our workflows dance, oh what a sight!
Dependencies updated, all in line,
Hopping forward, feeling fine! 🌼

---

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

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

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.