RAG quickstart entry point passes an unsupported paths argument

Open Beginner friendly

#14,610 opened on Sep 25, 2026 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 1/5
Estimated time: Under an hour
Newbie friendliness: 92/100

Issue type: Bug
Clarity: Clearly specified
Activity status: Active
Tech stack: google-cloud, python
Domain: ai

Research direction

Open generative_ai/rag/quickstart_example.py and inspect the main block together with the quickstart definition. Run the sample entry point or the reported static call check to confirm the mismatch. Done means the command-line sample passes the supported gcs_path argument and no longer raises the unexpected-keyword error.

Written by the indexing model from the issue text.

Description

samples

In which file did you encounter the issue?

generative_ai/rag/quickstart_example.py

Did you change the file? If so, how?

No.

Describe the issue

Running the sample entry point reaches the __main__ block and calls quickstart with a paths keyword:

quickstart(
    display_name="test_corpus_quickstart",
    paths=[gdrive_path, gcloud_path],
)

The function is defined as quickstart(display_name, gcs_path), so the sample fails before making an API request.

Reproduction output:

TypeError: quickstart() got an unexpected keyword argument 'paths'

The same mismatch is visible with a static call check:

quickstart_example.py:147: error: Unexpected keyword argument "paths" for "quickstart"  [call-arg]

Expected behavior: the command-line sample invokes quickstart with the supported gcs_path argument. Actual behavior: it raises TypeError and cannot run.

Environment: Python 3.12, repository main at commit 430a87ada6f2d33f318b5d16b77464679905a140.

Dominant language: Jupyter Notebook
Stars: 8.1k
Forks: 6.7k
Avg merge: 4d 4h
Merged PRs (30d): 8

Contributor guide

Open the contributing guide

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Similar issues

FunctionInvokingChatClient: default rejection message causes models to re-request approval for an already-rejected tool call Open

area-ai untriaged

Difficulty 2/5 1-3 hours Newbie friendliness 78/100

dotnet/extensions#7783 · Opened Sep 25, 2026
kimi models via OpenRouter lose reasoning continuity: _REASONING_ECHO_RULES kimi rule has no model-name fallback Open

comp/agent P2 provider/kimi provider/openrouter type/bug

Difficulty 2/5 1-3 hours Newbie friendliness 78/100

NousResearch/hermes-agent#122303 · 1 comment · Opened Sep 25, 2026
normalize_facts mishandles wrapped {facts: [...]} objects and bare strings Open

sdk-python

Difficulty 2/5 1-3 hours Newbie friendliness 75/100

mem0ai/mem0#7446 · 1 comment · Opened Sep 25, 2026
[missing-model] zai-coding-plan: glm-5.3-flashx Open

Difficulty 2/5 1-3 hours Newbie friendliness 72/100

anomalyco/models.dev#8058 · 1 comment · Opened Sep 25, 2026
@openclaw/kimi-provider: kimi-for-coding thinking profile stuck at off/on — K2.8 Preview supports low/high/max Open

clawsweeper:needs-maintainer-review clawsweeper:needs-product-decision clawsweeper:no-new-fix-pr clawsweeper:source-repro impact:auth-provider issue-rating: 🦞 diamond lobster P2

Difficulty 2/5 1-3 hours Newbie friendliness 76/100

openclaw/openclaw#157781 · 2 comments · 1 reaction · Opened Sep 25, 2026

More AI Infra & Agents issues