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

Client should be able to handle None on key values.

Open
#14 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
api

Research direction

Start with typesense/documents.py, especially documents.upsert, and follow the request path into typesense/api_call.py where the reported error is raised. Reproduce an upsert containing a Python None value for a key and clarify the intended graceful handling; done means the request no longer fails with the reported malformed-field error.

Written by the indexing model from the issue text.

Description

Description

Client should be able to handle None on key values.

  File "/site-packages/typesense/documents.py", line 42, in upsert
    return self.api_call.post(self._endpoint_path(), document, params)
  File "/site-packages/typesense/api_call.py", line 145, in post
    timeout=self.config.connection_timeout_seconds)
  File "/site-packages/typesense/api_call.py", line 115, in make_request
    raise ApiCall.get_exception(r.status_code)(r.status_code, error_message)
typesense.exceptions.RequestMalformed: [Errno 400] Field `xyz` must be a string.

Steps to reproduce

Send a Python None value for some key in the call documents.upsert(document)

Expected Behavior

Gracefully handle None value for a key

Typsense Version:
0.21

Dominant language
Python
Stars
247
Forks
66
Avg merge
22h 47m
Merged PRs (30d)
8

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 typesense/typesense-python

All issues in typesense/typesense-python

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.