[PR #21112] [MERGED] fix: handle null data in model_response_handler #41564

New Issue

GiteaMirror · 2026-04-25T13:45:42-05:00

GiteaMirror commented

2026-04-25 13:45:42 -05:00

📋 Pull Request Information

Original PR: https://github.com/open-webui/open-webui/pull/21112
Author: @silentoplayz
Created: 2/2/2026
Status: ✅ Merged
Merged: 2/5/2026
Merged by: @tjbck

Base: dev ← Head: fix/channel-message-model-response-null-data

📝 Commits (1)

95f9ced fix: handle null data in model_response_handler

📊 Changes

1 file changed (+1 additions, -1 deletions)

View changed files

📝 backend/open_webui/routers/channels.py (+1 -1)

📄 Description

Pull Request Checklist

Note to first-time contributors: Please open a discussion post in Discussions to discuss your idea/fix with the community before creating a pull request, and describe your changes before submitting a pull request.

This is to ensure large feature PRs are discussed with the community first, before starting work on it. If the community does not want this feature or it is not relevant for Open WebUI as a project, it can be identified in the discussion before working on the feature and submitting the PR.

Before submitting, make sure you've checked the following:

Target branch: Verify that the pull request targets the dev branch. PRs targeting main will be immediately closed.
Description: Provide a concise description of the changes made in this pull request down below.
Changelog: Ensure a changelog entry following the format of Keep a Changelog is added at the bottom of the PR description.
Documentation: Add docs in Open WebUI Docs Repository. Document user-facing behavior, environment variables, public APIs/interfaces, or deployment steps.
Dependencies: Are there any new or upgraded dependencies? If so, explain why, update the changelog/docs, and include any compatibility notes. Actually run the code/function that uses updated library to ensure it doesn't crash.
Testing: Perform manual tests to verify the implemented fix/feature works as intended AND does not break any other functionality. Include reproducible steps to demonstrate the issue before the fix. Test edge cases (URL encoding, HTML entities, types). Take this as an opportunity to make screenshots of the feature/fix and include them in the PR description.
Agentic AI Code: Confirm this Pull Request is not written by any AI Agent or has at least gone through additional human review AND manual testing. If any AI Agent is the co-author of this PR, it may lead to immediate closure of the PR.
Code review: Have you performed a self-review of your code, addressing any coding standard issues and ensuring adherence to the project's coding standards?
Design & Architecture: Prefer smart defaults over adding new settings; use local state for ephemeral UI logic. Open a Discussion for major architectural or UX changes.
Git Hygiene: Keep PRs atomic (one logical change). Clean up commits and rebase on dev to ensure no unrelated commits (e.g. from main) are included. Push updates to the existing PR branch instead of closing and reopening.
Title Prefix: To clearly categorize this pull request, prefix the pull request title using one of the following:
- BREAKING CHANGE: Significant changes that may affect compatibility
- build: Changes that affect the build system or external dependencies
- ci: Changes to our continuous integration processes or workflows
- chore: Refactor, cleanup, or other non-functional code changes
- docs: Documentation update or addition
- feat: Introduces a new feature or enhancement to the codebase
- fix: Bug fix or error correction
- i18n: Internationalization or localization changes
- perf: Performance improvement
- refactor: Code restructuring for better maintainability, readability, or scalability
- style: Changes that do not affect the meaning of the code (white space, formatting, missing semi-colons, etc.)
- test: Adding missing tests or correcting existing tests
- WIP: Work in progress, a temporary label for incomplete or ongoing work

Changelog Entry

Description

Fix AttributeError in model_response_handler when processing channel messages. The function iterates over thread messages to build conversation history for model responses, but some messages in the channel may have a null data field, causing a crash when accessing thread_message.data.get("files", []).

Fixed

Fixed AttributeError: 'NoneType' object has no attribute 'get' in model_response_handler at backend/open_webui/routers/channels.py:1068 when channel messages have null data field. Added null-safe check using (thread_message.data or {}).get("files", []).

Additional Information

Why fix in channels.py instead of downstream code (e.g., actions): The model_response_handler function is core channel infrastructure used throughout the application to auto-trigger model responses when mentioned via <@M:model-id|model-name> format. The bug affects any use of this function, not just action functions.

The issue occurs when iterating over thread messages to build conversation history - some older messages in channels may have data=None (data consistency issue from before schema updates). The proper fix is in the core code where the bug exists, not in downstream consumers that correctly call this function.

Alternative approaches considered:
1. Fix in action (rejected): Would require duplicating model response logic or wrapping in try/except, leaving the bug for other callers
2. Data migration (out of scope): Could update all null data fields, but doesn't address root cause and requires database migration
3. Fix in core (chosen): Minimal one-line null check prevents crashes for all callers without changing behavior
Related to channel messaging feature and model mention notifications.

Screenshots or Videos

Before

After

Contributor License Agreement

By submitting this pull request, I confirm that I have read and fully agree to the Contributor License Agreement (CLA), and I am providing my contributions under its terms.

Note

Deleting the CLA section will lead to immediate closure of your PR and it will not be merged in.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/open-webui/open-webui/pull/21112 **Author:** [@silentoplayz](https://github.com/silentoplayz) **Created:** 2/2/2026 **Status:** ✅ Merged **Merged:** 2/5/2026 **Merged by:** [@tjbck](https://github.com/tjbck) **Base:** `dev` ← **Head:** `fix/channel-message-model-response-null-data` --- ### 📝 Commits (1) - [`95f9ced`](https://github.com/open-webui/open-webui/commit/95f9ced1592bb0d82610797c59b7522cd52ad31d) fix: handle null data in model_response_handler ### 📊 Changes **1 file changed** (+1 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `backend/open_webui/routers/channels.py` (+1 -1) </details> ### 📄 Description  # Pull Request Checklist ### Note to first-time contributors: Please open a discussion post in [Discussions](https://github.com/open-webui/open-webui/discussions) to discuss your idea/fix with the community before creating a pull request, and describe your changes before submitting a pull request. This is to ensure large feature PRs are discussed with the community first, before starting work on it. If the community does not want this feature or it is not relevant for Open WebUI as a project, it can be identified in the discussion before working on the feature and submitting the PR. **Before submitting, make sure you've checked the following:** - [X] **Target branch:** Verify that the pull request targets the `dev` branch. **PRs targeting `main` will be immediately closed.** - [X] **Description:** Provide a concise description of the changes made in this pull request down below. - [X] **Changelog:** Ensure a changelog entry following the format of [Keep a Changelog](https://keepachangelog.com/) is added at the bottom of the PR description. - [X] **Documentation:** Add docs in [Open WebUI Docs Repository](https://github.com/open-webui/docs). Document user-facing behavior, environment variables, public APIs/interfaces, or deployment steps. - [X] **Dependencies:** Are there any new or upgraded dependencies? If so, explain why, update the changelog/docs, and include any compatibility notes. Actually run the code/function that uses updated library to ensure it doesn't crash. - [X] **Testing:** Perform manual tests to **verify the implemented fix/feature works as intended AND does not break any other functionality**. Include reproducible steps to demonstrate the issue before the fix. Test edge cases (URL encoding, HTML entities, types). Take this as an opportunity to **make screenshots of the feature/fix and include them in the PR description**. - [X] **Agentic AI Code:** Confirm this Pull Request is **not written by any AI Agent** or has at least **gone through additional human review AND manual testing**. If any AI Agent is the co-author of this PR, it may lead to immediate closure of the PR. - [X] **Code review:** Have you performed a self-review of your code, addressing any coding standard issues and ensuring adherence to the project's coding standards? - [X] **Design & Architecture:** Prefer smart defaults over adding new settings; use local state for ephemeral UI logic. Open a Discussion for major architectural or UX changes. - [X] **Git Hygiene:** Keep PRs atomic (one logical change). Clean up commits and rebase on `dev` to ensure no unrelated commits (e.g. from `main`) are included. Push updates to the existing PR branch instead of closing and reopening. - [X] **Title Prefix:** To clearly categorize this pull request, prefix the pull request title using one of the following: - **BREAKING CHANGE**: Significant changes that may affect compatibility - **build**: Changes that affect the build system or external dependencies - **ci**: Changes to our continuous integration processes or workflows - **chore**: Refactor, cleanup, or other non-functional code changes - **docs**: Documentation update or addition - **feat**: Introduces a new feature or enhancement to the codebase - **fix**: Bug fix or error correction - **i18n**: Internationalization or localization changes - **perf**: Performance improvement - **refactor**: Code restructuring for better maintainability, readability, or scalability - **style**: Changes that do not affect the meaning of the code (white space, formatting, missing semi-colons, etc.) - **test**: Adding missing tests or correcting existing tests - **WIP**: Work in progress, a temporary label for incomplete or ongoing work # Changelog Entry ### Description Fix `AttributeError` in `model_response_handler` when processing channel messages. The function iterates over thread messages to build conversation history for model responses, but some messages in the channel may have a `null` data field, causing a crash when accessing `thread_message.data.get("files", [])`. ### Fixed - Fixed `AttributeError: 'NoneType' object has no attribute 'get'` in `model_response_handler` at `backend/open_webui/routers/channels.py:1068` when channel messages have null data field. Added null-safe check using `(thread_message.data or {}).get("files", [])`. --- ### Additional Information - **Why fix in `channels.py` instead of downstream code (e.g., actions):** The `model_response_handler` function is core channel infrastructure used throughout the application to auto-trigger model responses when mentioned via `<@M:model-id|model-name>` format. The bug affects any use of this function, not just action functions. The issue occurs when iterating over thread messages to build conversation history - some older messages in channels may have `data=None` (data consistency issue from before schema updates). The proper fix is in the core code where the bug exists, not in downstream consumers that correctly call this function. Alternative approaches considered: 1. **Fix in action (rejected):** Would require duplicating model response logic or wrapping in try/except, leaving the bug for other callers 2. **Data migration (out of scope):** Could update all null data fields, but doesn't address root cause and requires database migration 3. **Fix in core (chosen):** Minimal one-line null check prevents crashes for all callers without changing behavior Related to channel messaging feature and model mention notifications. ### Screenshots or Videos ### Before <img width="2305" height="1271" alt="image" src="https://github.com/user-attachments/assets/db52779a-d37e-43ed-86a6-9aa61bb9aa94" /> ### After <img width="2305" height="1271" alt="image" src="https://github.com/user-attachments/assets/54572f09-177e-4a18-b0fb-21414b38e77d" /> ### Contributor License Agreement  By submitting this pull request, I confirm that I have read and fully agree to the [Contributor License Agreement (CLA)](https://github.com/open-webui/open-webui/blob/main/CONTRIBUTOR_LICENSE_AGREEMENT), and I am providing my contributions under its terms. > [!NOTE] > Deleting the CLA section will lead to immediate closure of your PR and it will not be merged in. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

GiteaMirror added the pull-request label 2026-04-25 13:45:42 -05:00

GiteaMirror closed this issue

2026-04-25 13:45:43 -05:00

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/open-webui#41564