Skip to content

Conversation

@thucpn
Copy link
Collaborator

@thucpn thucpn commented Jun 12, 2025

Summary by CodeRabbit

  • Chores
    • Removed end-to-end testing for the Python environment from the workflow.
    • Limited TypeScript end-to-end tests to run only on macOS, focusing on a specific datasource and template type.
    • Disabled several use cases in the test suite to focus testing on a single scenario.
    • Locked a development dependency to a specific version for improved consistency.

@changeset-bot
Copy link

changeset-bot bot commented Jun 12, 2025

⚠️ No Changeset found

Latest commit: 5d4a374

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

@thucpn thucpn marked this pull request as ready for review June 12, 2025 05:28
@coderabbitai
Copy link

coderabbitai bot commented Jun 12, 2025

Walkthrough

The GitHub Actions workflow file was updated to remove the entire e2e-python job, which previously handled Python end-to-end tests across multiple operating systems. Additionally, the e2e-typescript job was modified to run only on macos-latest with a reduced matrix of datasources and template types. In the TypeScript e2e tests, three use cases were commented out, limiting tests to only the "agentic_rag" use case.

Changes

File Change Summary
.github/workflows/e2e.yml Removed e2e-python job; restricted e2e-typescript job to run only on macos-latest OS with limited datasources and template types, and narrowed Node.js versions.
packages/create-llama/e2e/shared/llamaindexserver_template.spec.ts Commented out three use cases in templateUseCases array, restricting tests to only "agentic_rag".
packages/create-llama/templates/types/llamaindexserver/nextjs/package.json Locked tsx devDependency version from "^4.7.2" to exact "4.7.2".

Sequence Diagram(s)

sequenceDiagram
    participant Developer
    participant GitHub Actions
    participant macOS Runner

    Developer->>GitHub Actions: Push code / PR
    GitHub Actions->>macOS Runner: Trigger e2e-typescript job (macos-latest, --llamacloud, llamaindexserver)
    macOS Runner-->>GitHub Actions: Report test results
Loading

Possibly related PRs

  • refactor: e2e tests #256: Modifies .github/workflows/e2e.yml by removing or narrowing template types and environment variables in the test matrix, closely related to workflow simplification here.
  • feat: add test and fix python dependencies #304: Adds a Python dependency resolution test job while this PR removes the Python e2e job, both changing the same workflow file with opposite approaches to Python tests.
  • fix llamacloud issue #636: Changes the same TypeScript e2e test file by modifying use cases and environment variables, directly related to test coverage adjustments in llamaindexserver_template.spec.ts.

Suggested reviewers

  • leehuwuj
  • marcusschiesser

Poem

The Python tests have hopped away,
Typescript runs on Mac today.
Fewer OSes in the race,
A streamlined workflow takes their place.
In the garden of CI, swift and neat—
The code hops forward, light on its feet! 🐇✨


📜 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 e13d544 and 5d4a374.

📒 Files selected for processing (1)
  • packages/create-llama/templates/types/llamaindexserver/nextjs/package.json (1 hunks)
✅ Files skipped from review due to trivial changes (1)
  • packages/create-llama/templates/types/llamaindexserver/nextjs/package.json
⏰ Context from checks skipped due to timeout of 90000ms (5)
  • GitHub Check: Type Check
  • GitHub Check: Unit Tests (ubuntu-latest, 3.9)
  • GitHub Check: Unit Tests (windows-latest, 3.9)
  • GitHub Check: typescript (20, 3.11, macos-latest, nextjs, --llamacloud, llamaindexserver)
  • GitHub Check: lint

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

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 3

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between ae79064 and 33205ab.

📒 Files selected for processing (1)
  • .github/workflows/e2e.yml (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (5)
  • GitHub Check: typescript (22, 3.11, macos-latest, nextjs, --llamacloud, llamaindexserver)
  • GitHub Check: typescript (20, 3.11, macos-latest, nextjs, --llamacloud, llamaindexserver)
  • GitHub Check: lint
  • GitHub Check: Unit Tests (windows-latest, 3.9)
  • GitHub Check: Unit Tests (ubuntu-latest, 3.9)

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🔭 Outside diff range comments (1)
.github/workflows/e2e.yml (1)

88-90: ⚠️ Potential issue

Expression syntax will break for the template-types key

${{ matrix.template-types }} is invalid because the key contains a hyphen.
GitHub expressions require bracket notation for such keys.

-          TEMPLATE_TYPE: ${{ matrix.template-types }}
+          TEMPLATE_TYPE: ${{ matrix['template-types'] }}
♻️ Duplicate comments (3)
.github/workflows/e2e.yml (3)

23-23: OS matrix cut to a single platform – same concern as before
This comment duplicates feedback already given in a previous review about losing Windows + Ubuntu coverage.


25-25: Datasources matrix narrowed – same concern as before
Identical to the earlier comment flagging loss of --no-files and --example-file scenarios.


26-26: Template types trimmed – same concern as before
Repeats the earlier warning about skipping “streaming” templates.

🧹 Nitpick comments (3)
.github/workflows/e2e.yml (1)

21-21: Loss of Node.js v22 coverage

Shrinking the matrix to only Node 20 drops validation on the current LTS (v22). If any of the tooling bumps its minimum Node version, we will miss it until production.

Consider keeping both major versions:

-        node-version: [20]
+        node-version: [20, 22]
packages/create-llama/e2e/shared/llamaindexserver_template.spec.ts (2)

27-30: Commenting-out three use-cases slashes test coverage

Removing financial_report, deep_research, and code_generator means we’ll no longer detect regressions specific to those flows. If the runtime cost is the issue, consider selectively running them on a cron schedule rather than dropping them entirely.


90-94: Dead skip conditions

The test.skip clause still references financial_report and deep_research, which are now commented out above. This condition will never match and can be removed to reduce noise.

-          useCase === "financial_report" ||
-          useCase === "deep_research" ||
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 33205ab and e13d544.

📒 Files selected for processing (2)
  • .github/workflows/e2e.yml (1 hunks)
  • packages/create-llama/e2e/shared/llamaindexserver_template.spec.ts (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (4)
  • GitHub Check: lint
  • GitHub Check: typescript (20, 3.11, macos-latest, nextjs, --llamacloud, llamaindexserver)
  • GitHub Check: Unit Tests (ubuntu-latest, 3.9)
  • GitHub Check: Unit Tests (windows-latest, 3.9)

@thucpn
Copy link
Collaborator Author

thucpn commented Jun 12, 2025

Fixed in PR #686

@thucpn thucpn closed this Jun 12, 2025
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.

2 participants