Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Developer Knowledge fallback search response is not iterable

Open Beginner friendly
#14,609 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
88/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
python
Domain
backend, testing

Research direction

Start with developer-knowledge/conftest.py to inspect the fallback SearchDocumentChunksResponse, then compare its behavior with the iteration in developer-knowledge/search_document_chunks.py. Run python -m pytest developer-knowledge -q; done means all four focused tests pass and the fallback response can be used by the sample's pager loop.

Written by the indexing model from the issue text.

Description

samples

In which file did you encounter the issue?

developer-knowledge/conftest.py and developer-knowledge/search_document_chunks.py

Did you change the file? If so, how?

No.

Describe the issue

The Developer Knowledge samples include a fallback implementation for environments where the preview client is not installed. The fallback SearchDocumentChunksResponse stores its results but is not iterable, while the sample iterates over the response as a pager.

Reproduction command:

python -m pytest developer-knowledge -q

Result:

3 passed, 1 failed
...
developer-knowledge\\search_document_chunks.py:44: in search_document_chunks
    for chunk in response:
TypeError: 'SearchDocumentChunksResponse' object is not iterable

Expected behavior: all four focused tests pass using the intended fallback. Actual behavior: the search test fails before it can exercise the sample.

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

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

Getting set up

First steps

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

More from GoogleCloudPlatform/python-docs-samples

All issues in GoogleCloudPlatform/python-docs-samples

Similar issues

More Backend & API Design issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.