Skip to content

Conversation

@asimurka
Copy link

@asimurka asimurka commented Sep 24, 2025

Description

Removed unsupported <style> tags from Markdown tables to ensure compatibility with GitHub’s Markdown parser.

Type of change

  • Refactor
  • New feature
  • Bug fix
  • CVE fix
  • Optimization
  • Documentation Update
  • Configuration Update
  • Bump-up service version
  • Bump-up dependent library
  • Bump-up library or tool used for development (does not change the final image)
  • CI configuration change
  • Konflux configuration change
  • Unit tests improvement
  • Integration tests improvement
  • End to end tests improvement

Related Tickets & Documents

Checklist before requesting a review

  • I have performed a self-review of my code.
  • PR has passed all pre-merge test jobs.
  • If it is a core feature, I have added thorough tests.

Testing

  • Please provide detailed steps to perform tests related to this code change.
  • How were the fix/results from this change verified? Please provide relevant screenshots or results.

Summary by CodeRabbit

  • Documentation
    • Cleaned up provider documentation by removing inline styling to improve readability and consistency.
    • Updated the “Enabling a Llama Stack Provider” code sample with a trailing comma and clearer spacing to prevent formatting issues and improve copy-paste reliability.
    • No changes to public APIs.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Sep 24, 2025

Walkthrough

Documentation update: removed an inline CSS style block and adjusted a code sample in docs/providers.md by adding a trailing comma after "pymilvus>=2.4.10" and inserting an empty line. No code or public API changes.

Changes

Cohort / File(s) Summary
Docs cleanup
docs/providers.md
Removed inline CSS style block; in “Enabling a Llama Stack Provider” code sample, added a trailing comma after "pymilvus>=2.4.10" and inserted an empty line.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

Thump-thump! I tidied styles with care,
A comma hops in, light as air.
One line of space—ah, breathing room!
Docs now nibble less on gloom.
Carrot-coding done, I preen—so neat, so fair! 🥕✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check ✅ Passed The title "LCORE-424: Fixed documentation styling" succinctly captures the primary change in this PR, which removes unsupported <style> tags and minor Markdown styling fixes in docs/providers.md. It references the related issue and is concise without extraneous detail. This makes it an accurate and useful summary for reviewers scanning the repository history.
Docstring Coverage ✅ Passed No functions found in the changes. Docstring coverage check skipped.
✨ Finishing touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

  • Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
  • Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.


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

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Contributor

@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

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (6)
docs/providers.md (6)

217-223: YAML indentation is invalid for list item fields.

provider_type and config must be indented under the list item.

Apply this diff:

-        inference:
-            - provider_id: openai
-            provider_type: remote::openai
-            config:
-                api_key: ${env.OPENAI_API_KEY}
+        inference:
+          - provider_id: openai
+            provider_type: remote::openai
+            config:
+              api_key: ${env.OPENAI_API_KEY}

248-253: YAML list indentation under models looks off.

Ensure the model object is indented under models.

Apply this diff:

-    models:
-    - model_id: gpt-4-turbo  # local label
-        provider_id: openai
-        model_type: llm
-        provider_model_id: gpt-4-turbo  # provider label
+    models:
+      - model_id: gpt-4-turbo  # local label
+        provider_id: openai
+        model_type: llm
+        provider_model_id: gpt-4-turbo  # provider label

23-23: Fix typo: “atributes” → “attributes”.

Apply this diff:

-The tables below summarize each provider category, containing the following atributes:
+The tables below summarize each provider category, containing the following attributes:

231-231: Fix typo: “deffinition” → “definition”.

Apply this diff:

-**Note:** The `provider_type` attribute uses schema `<type>::<name>` and comes from the deffinition on upstream.
+**Note:** The `provider_type` attribute uses schema `<type>::<name>` and comes from the definition upstream.

39-39: Dependency name typo: itellm → litellm.

This will mislead users installing dependencies for Azure.

Apply this diff:

-| azure | remote | `itellm` | ❌ |
+| azure | remote | `litellm` | ❌ |

1-285: Remove leftover <style> block from docs/404.html

Found a <style> block at docs/404.html (lines 5–17) — remove it or externalize the CSS to avoid GitHub Markdown rendering issues.

🧹 Nitpick comments (7)
docs/providers.md (7)

67-67: Missing comma between dependencies.

Add a comma after mcp>=1.8.1 for consistency/readability.

Apply this diff:

-| meta-reference | inline | `matplotlib`, `pillow`, `pandas`, `scikit-learn`, `mcp>=1.8.1` `aiosqlite`, `psycopg2-binary`, `redis`, `pymongo` | ✅ |
+| meta-reference | inline | `matplotlib`, `pillow`, `pandas`, `scikit-learn`, `mcp>=1.8.1`, `aiosqlite`, `psycopg2-binary`, `redis`, `pymongo` | ✅ |

37-37: Normalize dependency list formatting.

Use commas between packages for consistency.

Apply this diff:

-| sentence-transformers | inline | `torch torchvision torchao>=0.12.0 --extra-index-url https://download.pytorch.org/whl/cpu`, `sentence-transformers --no-deps` | ❌ |
+| sentence-transformers | inline | `torch`, `torchvision`, `torchao>=0.12.0 --extra-index-url https://download.pytorch.org/whl/cpu`, `sentence-transformers --no-deps` | ❌ |

124-126: Split combined package name and fix spacing.

Present torch and torchtune separately; add spaces after commas.

Apply this diff:

-| torchtune-cpu | inline | `numpy`, `torch torchtune>=0.5.0`, `torchao>=0.12.0 --extra-index-url https://download.pytorch.org/whl/cpu`| ❌ |
-| torchtune-gpu | inline | `numpy`,`torch torchtune>=0.5.0`, `torchao>=0.12.0` | ❌ |
+| torchtune-cpu | inline | `numpy`, `torch`, `torchtune>=0.5.0`, `torchao>=0.12.0 --extra-index-url https://download.pytorch.org/whl/cpu` | ❌ |
+| torchtune-gpu | inline | `numpy`, `torch`, `torchtune>=0.5.0`, `torchao>=0.12.0` | ❌ |

80-80: Unify heading casing: DatasetIO vs Datasetio.

Use DatasetIO to match the ToC and other references.

Apply this diff:

-## Datasetio Providers
+## DatasetIO Providers

152-152: Tiny formatting nit: add space after comma.

Apply this diff:

-| rag-runtime | inline | `chardet`,`pypdf`, `tqdm`, `numpy`, `scikit-learn`, `scipy`, `nltk`, `sentencepiece`, `transformers` | ❌ |
+| rag-runtime | inline | `chardet`, `pypdf`, `tqdm`, `numpy`, `scikit-learn`, `scipy`, `nltk`, `sentencepiece`, `transformers` | ❌ |

215-215: Remove extra spacing in bolded phrase.

Apply this diff:

-    Add the provider instance under the **corresponding**       providers section:
+    Add the provider instance under the **corresponding** providers section:

190-194: Remove trailing comma in TOML array (docs/providers.md:190-194).

Python's tomllib parses the trailing comma (verified), but some TOML parsers are stricter — remove it to make the snippet copy/paste-safe.

-   llslibdev = [
-   "openai>=1.0.0",
-   "pymilvus>=2.4.10",
-   
-   # add your dependencies here
-   ]
+   llslibdev = [
+     "openai>=1.0.0",
+     "pymilvus>=2.4.10"
+     # add your dependencies here
+   ]
📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 0edd764 and 6c29f14.

📒 Files selected for processing (1)
  • docs/providers.md (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)
  • GitHub Check: build-pr
  • GitHub Check: e2e_tests

Copy link
Contributor

@tisnik tisnik left a comment

Choose a reason for hiding this comment

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

LGTM

@tisnik tisnik merged commit 6c47356 into lightspeed-core:main Sep 24, 2025
18 of 19 checks passed
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