Skip to content

Fix format for doom 1.9#7

Merged
fyuan1316 merged 1 commit intomasterfrom
format-doom_1.9
Jul 9, 2025
Merged

Fix format for doom 1.9#7
fyuan1316 merged 1 commit intomasterfrom
format-doom_1.9

Conversation

@fyuan1316
Copy link
Copy Markdown
Contributor

@fyuan1316 fyuan1316 commented Jul 9, 2025

Summary by CodeRabbit

  • Documentation

    • Improved formatting and clarity in the guides for extending LLM inference runtimes and model repository management.
    • Enhanced list structures and added detailed step-by-step instructions for Git command line uploads.
    • Refined headings and whitespace for better readability.
  • Chores

    • Updated the development dependency "@alauda/doom" to version ^1.9.0.

@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Jul 9, 2025

Walkthrough

This update refines documentation for model inference runtimes and model repository management by improving formatting, list structures, and clarity. Headings and lists are standardized, and Git upload instructions are expanded. Additionally, the "@alauda/doom" development dependency is updated in the package configuration.

Changes

Files/Paths Change Summary
docs/en/model_inference/inference_service/how_to/custom_inference_runtime.mdx Removed numeric prefixes from step headings; adjusted whitespace for improved readability.
docs/en/model_inference/model_management/functions/model_repository.mdx Reformatted lists with explicit numbering; expanded Git upload instructions with detailed steps.
package.json Updated "@alauda/doom" dev dependency from "^1.4.0" to "^1.9.0".

Possibly related PRs

Suggested reviewers

  • typhoonzero
  • zhaomingkun1030

Poem

In the docs a rabbit hops,
Tidying lists and headings—never stops!
With clearer steps and guides anew,
Even Git commands get a fresh view.
A version bumps, the carrots cheer,
Documentation’s crystal clear! 🥕✨


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.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

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
Copy Markdown

@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: 1

🔭 Outside diff range comments (1)
docs/en/model_inference/inference_service/how_to/custom_inference_runtime.mdx (1)

117-120: YAML likely invalid – stray - bash after script.

Inside the containers: stanza you already set:

command:
  - bash
  - -c
  - |
    # long script …

The extra list item on lines 119-120:

118 # see: …
119 - bash
120 resources:

adds a fourth element to command, turning resources: into a child of that list and breaking the manifest. Drop the stray - bash:

-            - bash
-            resources:
+            resources:

Kube-api-server will reject otherwise.

🧹 Nitpick comments (2)
docs/en/model_inference/model_management/functions/model_repository.mdx (1)

124-135: Warn users about destructive git lfs migrate import --above 100MB.

Good call mentioning history-rewrite, but newcomers may still run this in a shared repo and nuke colleagues’ work. Consider adding an explicit caution line:

> ⚠️  **History rewrite ahead** – run this *only* before the first push, or coordinate a force-push with all collaborators.

Helps avoid accidental data loss.

docs/en/model_inference/inference_service/how_to/custom_inference_runtime.mdx (1)

35-43: Minor spacing: “” tag should be followed by a blank line.

Some MDX processors treat <Steps> as a custom component needing a trailing newline; otherwise the first heading may stick to the tag. Just add one empty line after <Steps> to be safe.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 907acf8 and 8677c94.

⛔ Files ignored due to path filters (1)
  • yarn.lock is excluded by !**/yarn.lock, !**/*.lock
📒 Files selected for processing (3)
  • docs/en/model_inference/inference_service/how_to/custom_inference_runtime.mdx (3 hunks)
  • docs/en/model_inference/model_management/functions/model_repository.mdx (2 hunks)
  • package.json (1 hunks)
🧰 Additional context used
🪛 LanguageTool
docs/en/model_inference/model_management/functions/model_repository.mdx

[grammar] ~10-~10: Use correct spacing
Context: ...ges via commits/branches/tags, ensuring reproducibility. High-Speed Transfers - CLI/Notebook...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[grammar] ~13-~13: Use correct spacing
Context: ...ebook uploads leverage internal network bandwidth. Cross-Tenant Sharing - Shared models ...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[grammar] ~16-~16: Use correct spacing
Context: ...s namespaces (e.g., public as a model marketplace). Seamless Integration - Directly deplo...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[grammar] ~19-~19: Use correct spacing
Context: ...models from the repository to inference services. ## Core Features **Model Repository Creati...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[grammar] ~24-~24: Use correct spacing
Context: ...hecks (e.g., ensure no active inference services). File Management 1. *Web UI Upload...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[grammar] ~31-~31: Use correct spacing
Context: ... files (e.g., *.bin, *.h5). - Example: bash git clone <model_repo_url> git lfs install cp ~/local_model/* . && git add . && git commit -m "v1.0" && git push Version Control 1. Branching ...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[grammar] ~44-~44: Use correct spacing
Context: ...E.md` from the default branch for model descriptions. Cross-Tenant Sharing 1. **Shared Mo...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[grammar] ~50-~50: Use articles correctly
Context: ...ss. 2. Public Marketplace - Use public namespace to publish open-sour...

(QB_NEW_EN_OTHER_ERROR_IDS_11)


[grammar] ~50-~50: There might be a problem here.
Context: ...ce to publish open-source models (e.g., HuggingFace conversions). Integration with MLOps 1. **Deploym...

(QB_NEW_EN_MERGED_MATCH)


[grammar] ~56-~56: Use correct spacing
Context: ... models directly into AML Notebooks for testing: bash !git clone https://aml-public/resnet50.git ## Technical Notes 1. **Git LFS Requiremen...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[grammar] ~66-~66: Use correct spacing
Context: ...README.md` metadata may block inference deployment. ## Create Model Repository ### S...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[grammar] ~90-~90: There might be a mistake here.
Context: ...the File Management interface to upload files * Drag and drop files/folders into ...

(QB_NEW_EN_OTHER)


[grammar] ~91-~91: There might be a mistake here.
Context: ... drop files/folders into the designated area * Supported formats: All model file...

(QB_NEW_EN_OTHER)


[grammar] ~93-~93: Use correct spacing
Context: ...Progress tracking with real-time upload status * Option 2: Git Command Line Upload ...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[grammar] ~95-~95: Use correct spacing
Context: ... status * Option 2: Git Command Line Upload 1. Get Repository Address: * Nav...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[grammar] ~98-~98: There might be a mistake here.
Context: ... * Navigate to Detail Info → Basic Info * Copy the Git repository URL (...

(QB_NEW_EN_OTHER)


[grammar] ~99-~99: There might be a mistake here.
Context: ... * Copy the Git repository URL (e.g., https://<your-domain>/<namespace>/<repo-name>.git) 2. Upload via Git: ```bash # Clone the...

(QB_NEW_EN_OTHER)


[grammar] ~101-~101: Use correct spacing
Context: ...<repo-name>.git) 2. Upload via Git: bash # Clone the repository git clone <repository-url> # Navigate to repo directory cd <repo-name> # Initialize Git LFS (if not already set up) git lfs install # Add model files (replace with your actual files) cp -r /path/to/your/model/files/* . # Configure LFS tracking (for large files) git lfs track "*.h5" "*.bin" "*.pt" # Commit and push git add . git commit -m "Add model files v1.0" # Perform LFS migration check for existing large files (as seen in screenshot) git lfs migrate info # Migrate existing large files to LFS, specifically those above 100MB. # NOTE: This command rewrites commit history. If the repository is already shared, # coordinate with collaborators and push with --force, or prefer running it # before the first public push. # This limit (100MB) is chosen based on GitHub's recommended file size limits # for optimal performance and handling, as documented at: # https://docs.github.com/en/repositories/working-with-files/managing-large-files/about-large-files-on-github#file-size-limits git lfs migrate import --above 100MB git push origin main

(QB_NEW_EN_OTHER_ERROR_IDS_5)

docs/en/model_inference/inference_service/how_to/custom_inference_runtime.mdx

[grammar] ~39-~39: Use correct spacing
Context: ... ### Create Inference Runtime Resources You'll need to create the corresponding...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[grammar] ~41-~41: Use correct spacing
Context: ...sed on your target hardware environment (GPU/CPU/NPU). 1. *Prepare the Runtime YAML Configuration...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[grammar] ~43-~43: Use correct spacing
Context: ...PU/NPU). 1. Prepare the Runtime YAML Configuration: Based on the type of runtime you want t...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[grammar] ~153-~153: Use correct spacing
Context: ...erence Inference Service and Select the Runtime Once the Xinference inference runtime r...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[grammar] ~155-~155: Use correct spacing
Context: ...ng your LLM inference service on the AI Platform. 1. **Configure Inference Framework for the M...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[grammar] ~157-~157: Use correct spacing
Context: ...Configure Inference Framework for the Model: Ensure that on the model details page o...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[grammar] ~160-~160: Use correct spacing
Context: ...ate to the Inference Service Publishing Page**: Log in to the AI Platform and navigate ...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[grammar] ~163-~163: Use correct spacing
Context: ...e Service." 3. Select the Xinference Runtime: In the inference service creation wizar...

(QB_NEW_EN_OTHER_ERROR_IDS_5)

🔇 Additional comments (1)
package.json (1)

3-3: Verify compatibility impact of bumping @alauda/doom to ^1.9.0.

Jumping from the 1.4.x range to 1.9.x can bring breaking changes in the Doom build pipeline (e.g., updated MDX processing rules, plugin renames). Please double-check:

  1. Local yarn dev / doom build still complete successfully.
  2. Any custom Doom plugins or theme overrides still resolve.
  3. The generated site in CI remains identical (diff HTML output).

If everything looks green, feel free to ignore.

Signed-off-by: Yuan Fang <yuanfang@alauda.io>
Copy link
Copy Markdown

@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

🧹 Nitpick comments (2)
docs/en/model_inference/model_management/functions/model_repository.mdx (1)

8-19: Consolidate headline & bullet into one list item for cleaner MDX

The headline is rendered as a paragraph and its description as a separate bullet. Collapsing them into a single bullet keeps the list tight and avoids awkward spacing.

-**Git-native Version Control**  
-- Track model changes via commits/branches/tags, ensuring reproducibility.  
+ - **Git-native Version Control**: Track model changes via commits/branches/tags, ensuring reproducibility.

Repeat the same pattern for High-Speed Transfers, Cross-Tenant Sharing, and Seamless Integration to maintain consistency.

docs/en/model_inference/inference_service/how_to/custom_inference_runtime.mdx (1)

43-44: Nest numbered sub-steps two spaces deeper for proper Markdown hierarchy

Inside a <Steps> block, any ordered list that belongs to the current step should be indented by two spaces. Without the indent, Markdown starts a new top-level list, which breaks the auto-numbering in Docusaurus.

-1. **Prepare the Runtime YAML Configuration**:
+  1. **Prepare the Runtime YAML Configuration**:

-2.  **Apply the YAML File to Create the Resource**:
+  2. **Apply the YAML File to Create the Resource**:

Same rule applies to similar sub-steps later in the file.

Also applies to: 142-144

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 8677c94 and 72bdf0d.

⛔ Files ignored due to path filters (1)
  • yarn.lock is excluded by !**/yarn.lock, !**/*.lock
📒 Files selected for processing (3)
  • docs/en/model_inference/inference_service/how_to/custom_inference_runtime.mdx (3 hunks)
  • docs/en/model_inference/model_management/functions/model_repository.mdx (2 hunks)
  • package.json (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • package.json
🧰 Additional context used
🪛 LanguageTool
docs/en/model_inference/inference_service/how_to/custom_inference_runtime.mdx

[grammar] ~39-~39: Use correct spacing
Context: ... ### Create Inference Runtime Resources You'll need to create the corresponding...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[grammar] ~41-~41: Use correct spacing
Context: ...sed on your target hardware environment (GPU/CPU/NPU). 1. *Prepare the Runtime YAML Configuration...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[grammar] ~43-~43: Use correct spacing
Context: ...PU/NPU). 1. Prepare the Runtime YAML Configuration: Based on the type of runtime you want t...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[grammar] ~153-~153: Use correct spacing
Context: ...erence Inference Service and Select the Runtime Once the Xinference inference runtime r...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[grammar] ~155-~155: Use correct spacing
Context: ...ng your LLM inference service on the AI Platform. 1. **Configure Inference Framework for the M...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[grammar] ~157-~157: Use correct spacing
Context: ...Configure Inference Framework for the Model: Ensure that on the model details page o...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[grammar] ~160-~160: Use correct spacing
Context: ...ate to the Inference Service Publishing Page**: Log in to the AI Platform and navigate ...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[grammar] ~163-~163: Use correct spacing
Context: ...e Service." 3. Select the Xinference Runtime: In the inference service creation wizar...

(QB_NEW_EN_OTHER_ERROR_IDS_5)

docs/en/model_inference/model_management/functions/model_repository.mdx

[grammar] ~10-~10: Use correct spacing
Context: ...ges via commits/branches/tags, ensuring reproducibility. High-Speed Transfers - CLI/Notebook...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[grammar] ~13-~13: Use correct spacing
Context: ...ebook uploads leverage internal network bandwidth. Cross-Tenant Sharing - Shared models ...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[grammar] ~16-~16: Use correct spacing
Context: ...s namespaces (e.g., public as a model marketplace). Seamless Integration - Directly deplo...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[grammar] ~19-~19: Use correct spacing
Context: ...models from the repository to inference services. ## Core Features **Model Repository Creati...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[grammar] ~24-~24: Use correct spacing
Context: ...hecks (e.g., ensure no active inference services). File Management 1. *Web UI Upload...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[grammar] ~31-~31: Use correct spacing
Context: ... files (e.g., *.bin, *.h5). - Example: bash git clone <model_repo_url> git lfs install cp ~/local_model/* . && git add . && git commit -m "v1.0" && git push Version Control 1. Branching ...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[grammar] ~44-~44: Use correct spacing
Context: ...E.md` from the default branch for model descriptions. Cross-Tenant Sharing 1. **Shared Mo...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[grammar] ~50-~50: Use articles correctly
Context: ...ss. 2. Public Marketplace - Use public namespace to publish open-sour...

(QB_NEW_EN_OTHER_ERROR_IDS_11)


[grammar] ~50-~50: There might be a problem here.
Context: ...ce to publish open-source models (e.g., HuggingFace conversions). Integration with MLOps 1. **Deploym...

(QB_NEW_EN_MERGED_MATCH)


[grammar] ~56-~56: Use correct spacing
Context: ... models directly into AML Notebooks for testing: bash !git clone https://aml-public/resnet50.git ## Technical Notes 1. **Git LFS Requiremen...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[grammar] ~66-~66: Use correct spacing
Context: ...README.md` metadata may block inference deployment. ## Create Model Repository ### S...

(QB_NEW_EN_OTHER_ERROR_IDS_5)

🔇 Additional comments (1)
docs/en/model_inference/model_management/functions/model_repository.mdx (1)

89-138: Indentation fix looks good – nested list now renders correctly

The added four-space indent keeps Option 1 and Option 2 inside “Step 3”, resolving the rendering issue from the previous review.

@fyuan1316 fyuan1316 merged commit e26f82d into master Jul 9, 2025
2 checks passed
@JounQin JounQin deleted the format-doom_1.9 branch August 13, 2025 03:44
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.

1 participant