Updating the warnings

[Giom-V]

No description provided.

[review-notebook-app]

Check out this pull request on 

See visual diffs & provide feedback on Jupyter Notebooks.

---

Powered by ReviewNB

[gemini-code-assist]

Summary of Changes

Hello @Giom-V, 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 focuses on enhancing the user experience and consistency within the Jupyter notebooks by standardizing how warning messages are displayed. It transitions from verbose HTML table structures to concise Markdown blockquotes, making the warnings easier to read and integrate seamlessly into the notebook content. Additionally, it includes a general cleanup of one notebook's metadata and outputs.

Highlights

• Standardized Warning Format: Replaced custom HTML table-based warning badges with a consistent Markdown blockquote format across numerous Jupyter notebooks.
• Notebook Cleanup: Cleared execution counts and outputs, and updated metadata in gemini_google_adk_model_guardrails.ipynb for a cleaner state.
• Improved Readability: The new Markdown format enhances the readability and maintainability of warning messages within the notebooks.

Changelog

• examples/Classify_text_with_embeddings.ipynb
  • Replaced HTML pricing warning with a Markdown blockquote.
• examples/Google_IO2025_Live_Coding.ipynb
  • Replaced HTML Imagen pricing warning with a Markdown blockquote.
  • Replaced HTML Veo pricing warning with a Markdown blockquote.
• examples/Search_reranking_using_embeddings.ipynb
  • Replaced HTML pricing warning with a Markdown blockquote.
• examples/Talk_to_documents_with_embeddings.ipynb
  • Replaced HTML pricing warning with a Markdown blockquote.
• examples/anomaly_detection.ipynb
  • Replaced HTML pricing warning with a Markdown blockquote.
• examples/chromadb/Vectordb_with_chroma.ipynb
  • Replaced HTML pricing warning with a Markdown blockquote.
• examples/clustering_with_embeddings.ipynb
  • Replaced HTML pricing warning with a Markdown blockquote.
• examples/document_search.ipynb
  • Replaced HTML pricing warning with a Markdown blockquote.
• examples/gemini_google_adk_model_guardrails.ipynb
  • Updated cell metadata for consistency.
  • Cleared execution counts and outputs from various code cells.
  • Removed an empty line from a markdown cell.
• examples/langchain/Code_analysis_using_Gemini_LangChain_and_DeepLake.ipynb
  • Replaced HTML pricing warning with a Markdown blockquote.
• examples/langchain/Gemini_LangChain_QA_Chroma_WebLoad.ipynb
  • Replaced HTML pricing warning with a Markdown blockquote.
• examples/langchain/Gemini_LangChain_QA_Pinecone_WebLoad.ipynb
  • Replaced HTML pricing warning with a Markdown blockquote.
• examples/llamaindex/Gemini_LlamaIndex_QA_Chroma_WebPageReader.ipynb
  • Replaced HTML pricing warning with a Markdown blockquote.
• examples/qdrant/Hybrid_Search_Legal.ipynb
  • Replaced HTML pricing warning with a Markdown blockquote.
• examples/qdrant/Movie_Recommendation.ipynb
  • Replaced HTML pricing warning with a Markdown blockquote.
• examples/qdrant/Qdrant_similarity_search.ipynb
  • Replaced HTML pricing warning with a Markdown blockquote.
• examples/weaviate/personalized_description_with_weaviate_and_gemini_api.ipynb
  • Replaced HTML pricing warning with a Markdown blockquote.
• quickstarts/Get_started_Veo.ipynb
  • Replaced HTML pricing warning with a Markdown blockquote.
• quickstarts/Get_started_imagen.ipynb
  • Replaced HTML pricing warning with a Markdown blockquote.
• quickstarts/Get_started_imagen_rest.ipynb
  • Replaced HTML pricing warning with a Markdown blockquote.
• quickstarts/Template.ipynb
  • Replaced HTML pricing warning badge with a Markdown blockquote.
  • Replaced HTML notice badge with a Markdown blockquote.
• quickstarts/rest/Embeddings_REST.ipynb
  • Replaced HTML pricing warning with a Markdown blockquote.

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 standardizes the presentation of warnings and informational notes across multiple notebooks by replacing HTML table-based badges with a cleaner, more maintainable Markdown blockquote format. This is a positive change that improves the consistency and readability of the source files. Additionally, one notebook has undergone significant formatting cleanup, removing extraneous metadata and standardizing its structure, which is also a welcome improvement. The changes are well-executed and improve the overall quality of the codebase.