mirror of
https://github.com/open-webui/open-webui.git
synced 2026-05-07 03:18:23 -05:00
[PR #24256] [CLOSED] fix(web): guard xml_element_contents_to_string against None #66421
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/open-webui/open-webui/pull/24256
Author: @PHclaw
Created: 4/30/2026
Status: ❌ Closed
Base:
main← Head:fix/yandex-xml-none-check📝 Commits (1)
5effec6fix(web): guard xml_element_contents_to_string against None📊 Changes
1 file changed (+3 additions, -1 deletions)
View changed files
📝
backend/open_webui/retrieval/web/yandex.py(+3 -1)📄 Description
Summary
Fixes #24243
Bug
In
backend/open_webui/retrieval/web/yandex.py, thexml_element_contents_to_string()helper receiveselement: Elementbut is called with the result ofgroup.find('doc/url'),group.find('doc/title'), orgroup.find('doc/passages/passage'), any of which may returnNonewhen the corresponding XML node is absent.When
element is None, accessingelement.textraises:This crashes the entire search function, which then silently returns
[], so users see "No results found" even though the Yandex API returned valid results.Stack trace from the issue:
Fix
Guard against
Noneat the top of the helper:The function already handles the case of
element.textbeingNone(using''), so this change is consistent with the existing pattern.Impact
search_yandexfunction already hastry/exceptand returns[]on error, so this is a defensive improvement🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.