Fix AttributeError when metadata is null in request body - #17306
Merged
1 commit merged intoDec 2, 2025
Merged
Conversation
Handle the case where metadata is explicitly set to null/None in the
request body. This was causing a 401 error with "'NoneType' object
has no attribute 'get'" when calling /v1/batches with metadata: null.
The fix uses `or {}` instead of a default dict value since the key
exists but has a None value.
|
@Chesars is attempting to deploy a commit to the CLERKIEAI Team on Vercel. A member of the Team first needs to authorize it. |
fzowl
pushed a commit
to fzowl/litellm
that referenced
this pull request
Jun 24, 2026
…) (BerriAI#17306) Handle the case where metadata is explicitly set to null/None in the request body. This was causing a 401 error with "'NoneType' object has no attribute 'get'" when calling /v1/batches with metadata: null. The fix uses `or {}` instead of a default dict value since the key exists but has a None value.
This pull request was closed.
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
1 participant
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.
Title
Fix AttributeError when metadata is null in request body
Relevant issues
Fixes #17263
Pre-Submission checklist
Please complete all items before asking a LiteLLM maintainer to review your PR
tests/litellm/directory, Adding at least 1 test is a hardrequirement - see details
make test-unitType
🐛 Bug Fix
Changes
When sending a request to
/v1/batches(or other endpoints) withmetadata: null, the proxy returns a 401 error with:AttributeError: 'NoneType' object has no attribute 'get'In
get_tags_from_request_body(), the code usesrequest_body.get("metadata", {})which returnsNone(not{}) when the key exists with anullvalue. Thenmetadata.get("tags", [])fails.Fix: Changed to
request_body.get("metadata") or {}which correctly handles both missing keys and explicitnullvalues.Files changed:
litellm/proxy/common_utils/http_parsing_utils.py- Fix the null metadata handlingtests/test_litellm/proxy/common_utils/test_http_parsing_utils.py- Add regression testNo breaking changes