DA-1250: Fixing node version error in tests

[VirajAgarwal1]

The tests gave an error due to the new packages in vector-search-cookbook using ESM modules which wasn't fully supported in node version 18 used in CI pipeline.

[gemini-code-assist]

Summary of Changes

Hello @VirajAgarwal1, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request primarily focuses on minor formatting improvements within two Jupyter notebooks. The changes involve adjusting markdown heading levels to ensure consistent document structure and removing an extraneous blank line. While the PR title and description indicate a fix for a Node.js version error in tests, the provided patches only reflect these cosmetic notebook updates.

Highlights

• Notebook Formatting: Adjusted markdown heading levels in RAG_with_Capella_Model_Services_and_LangChain.ipynb and RAG_with_Couchbase_SmolAgents.ipynb from H1 to H2 for better document hierarchy.
• Whitespace Cleanup: Removed an unnecessary blank line from a code cell definition in RAG_with_Couchbase_SmolAgents.ipynb.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog

• capella-model-services/langchain/query_based/RAG_with_Capella_Model_Services_and_LangChain.ipynb
  • Updated the 'Introduction' markdown heading from H1 (#) to H2 (##).
• smolagents/query_based/RAG_with_Couchbase_SmolAgents.ipynb
  • Removed an empty line from a code cell definition.
  • Updated the 'Building a RAG Agent using smolagents' markdown heading from H1 (#) to H2 (##).

Activity

• No specific human activity (comments, reviews, or progress updates) has been recorded for this pull request yet.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request introduces minor stylistic changes in two Jupyter notebooks, adjusting markdown heading levels for better consistency. The changes are correct and improve the readability of the notebooks.

However, the pull request title and description state that this change is to fix a Node.js version error in tests. The provided code changes, which are limited to markdown formatting in Python notebooks, do not seem to align with this stated purpose. It would be helpful to update the pull request's title and description to accurately reflect the changes made.

For future improvements, I noticed that capella-model-services/langchain/search_based/RAG_with_Capella_Model_Services_and_LangChain.ipynb still uses a level 1 heading for its introduction. To maintain consistency across all notebooks, you might consider updating it in a separate pull request.