mirror of
https://github.com/deepseek-ai/DeepSeek-V3.git
synced 2026-11-05 00:47:48 +00:00
[GH-ISSUE #1336] Search engine broken: returns dictionary articles for "normal" and other junk #881
Labels
No labels
closed-as-stale
enhancement
question
spam
stale
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
deepseek-ai/DeepSeek-V3#881
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
Originally created by @kermyo on GitHub (May 19, 2026).
Original GitHub issue: https://github.com/deepseek-ai/DeepSeek-V3/issues/1336
Hi team,
I'm a heavy user of the DeepSeek web/app, and for the past 24 hours, the search filter has been completely broken for many queries.
What I expected to happen:
When I type a question or ask for specific info (e.g., "Tell me about the streamer MZLFF"), I expect the model to use online resources to find relevant biographical information.
What actually happens:
The model consistently returns completely irrelevant search results. For the same query, instead of a biography, it gets stuck on dictionary articles for the word "normal" (from Cambridge, Collins, Oxford), or public holiday calendars for Russia. This happens across multiple unrelated topics.
Steps to reproduce:
Ask a specific question: "Search the web for the biography of MZLFF."
Observe the model's response.
The model will always complain that it can only find linguistic articles about "normal" or irrelevant calendar data.
This started on May 2, 2026, and makes the online search feature completely unusable. Please investigate the filtering algorithm.
@qingkong66 commented on GitHub (May 19, 2026):
@kermyo
Confirmed. Search is returning irrelevant results (dictionary entries, holiday calendars) for queries that should fetch person/user information.
This is a core feature regression. The same query works correctly on other platforms.
No fix to offer, but your issue is on record. Should be escalated.
—
Update: your issue is on record.
@github-actions[bot] commented on GitHub (Jun 22, 2026):
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you believe this issue is still relevant, please leave a comment to keep it open. Thank you for your contributions!
@github-actions[bot] commented on GitHub (Jul 7, 2026):
false