Closed
Conversation
Update all hardcoded version references from 26.1.2 to 26.3.0-RC1 across helm charts, docker-compose, FastAPI, docs, and examples. Made-with: Cursor
…VIDIA#1577) Co-authored-by: Kurt Heiss <kheiss@nvidia.com>
Co-authored-by: Jeremy Dyer <jdye64@gmail.com>
…ing long VLM captioning Large PDFs with VLM captioning enabled can take 2-22+ hours depending on hardware. The previous defaults (STATE_TTL=7200s, RESULT_DATA_TTL=3600s) caused job state to expire mid-processing, resulting in 404 "Job ID not found or state has expired" errors even though the pipeline completed successfully. Raises both defaults to 172800s (48 hours), providing sufficient headroom for all observed workloads. Users can still override via RESULT_DATA_TTL_SECONDS and STATE_TTL_SECONDS environment variables. Fixes: Customer bug 5914605 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-authored-by: sosahi <syousefisahi@nvidia.com>
fix code syntax in faq
Kheiss/6000353 - update links to Helm chart (NVIDIA#1697)
…riever Library (NVIDIA#1715) removed inclusion of Python requirements in the support matrix
…t pipeline by removing references to deprecated PDF extractors and obsolete OCR API usage left over from the NeMo Retriever Library transition. (NVIDIA#1727)
Co-authored-by: sosahi <syousefisahi@nvidia.com>
…ine; misc README/Helm fixesUpdating files per bugs 5966185, 5966211, and 5966281 (NVIDIA#1742) Co-authored-by: sosahi <syousefisahi@nvidia.com>
Made-with: Cursor
Greptile Summary This PR ports documentation updates from PR NVIDIA#1812 to the 26.03 branch, refreshing the extraction overview (docs/docs/extraction/overview.md) and the library-mode quick start README (nemo_retriever/README.md) with CUDA 13 requirements, updated install commands, and new pipeline examples. nemo_retriever/README.md line 158: uv pip install -y openai uses an invalid -y flag — this is an apt/apt-get convention that uv pip install does not support, so the command will fail with an unrecognized option error for any user who follows the quick start guide. Confidence Score: 4/5 Safe to merge after fixing the invalid -y flag in the uv install command on line 158. One P1 finding: a broken shell command that will error when copy-pasted by users following the quick start guide. All other changes are prose-only documentation with no functional issues. nemo_retriever/README.md — invalid uv pip install -y openai on line 158. Important Files Changed Filename Overview docs/docs/extraction/overview.md Documentation-only overview update describing supported file types and related topics; no issues found. nemo_retriever/README.md Quick start README updated with CUDA 13 setup and pipeline examples; contains an invalid -y flag in a uv pip install command on line 158. Flowchart %%{init: {'theme': 'neutral'}}%% flowchart TD A["Input Documents\nPDF / DOCX / HTML / Audio / Video"] --> B["create_ingestor()"] B --> C[".files()"] C --> D[".extract()\nPage Elements + OCR + Table Structure"] D --> E{Optional Steps} E --> F[".split()\nToken-based chunking"] E --> G[".embed()\nEmbedding generation"] G --> H[".vdb_upload()\nLanceDB storage"] H --> I["Retriever.query()\nSemantic search"] I --> J["LLM Answer Generation"] Loading Comments Outside Diff (1) nemo_retriever/README.md, line 158 (link) P1 Invalid flag for uv pip install The -y flag is not recognized by uv pip install — it is an apt-get/apt convention, not a uv flag. Running this command will fail with an unrecognized option error for any user who copy-pastes it from the quick start guide. Prompt To Fix With AI This is a comment left during a code review. Path: nemo_retriever/README.md Line: 158 Comment: Invalid flag for uv pip install The -y flag is not recognized by uv pip install — it is an apt-get/apt convention, not a uv flag. Running this command will fail with an unrecognized option error for any user who copy-pastes it from the quick start guide. How can I resolve this? If you propose a fix, please make it concise. Prompt To Fix All With AI This is a comment left during a code review. Path: nemo_retriever/README.md Line: 158 Comment: Invalid flag for uv pip install The -y flag is not recognized by uv pip install — it is an apt-get/apt convention, not a uv flag. Running this command will fail with an unrecognized option error for any user who copy-pastes it from the quick start guide. uv pip install openai How can I resolve this? If you propose a fix, please make it concise. Description Checklist I am familiar with the Contributing Guidelines. New or existing tests cover these changes. The documentation is up to date with these changes. If adjusting docker-compose.yaml environment variables have you ensured those are mimicked in the Helm values.yaml file.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
8 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Checklist