AI Summary returns HTTP 500 when language is zh-CN, but works with English

Open
#5,139 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
ai

Research direction

The report identifies GET /ai/summary with language=zh-CN as the failing entry point, but names no source files or tests. Start by tracing that route’s locale handling and compare it with the working English request; reproduce the HTTP 500 and inspect the backend error. Done when Simplified Chinese summaries succeed and the regression is covered by a test.

Written by the indexing model from the issue text.

Description

bug platform: desktop
Platform

Desktop - Windows

Describe the bug

Environment: Folo Desktop 1.18.0, Folo Pro, Windows, OpenClash/Mihomo Fake-IP.

Steps to reproduce:

  1. Set Folo interface language to Simplified Chinese.
  2. Open any article and click AI Summary.
  3. GET /ai/summary?language=zh-CN&target=content returns HTTP 500.
  4. Switch interface language to English.
  5. Generate the summary again; it works normally.

Actual response: {"code":500,"message":"Internal Server Error"}
Expected: AI Summary should work in Simplified Chinese as well.

Please investigate the zh-CN locale-specific AI summary backend handling.

Entry ID

No response

Relevant Information

No response

Reproduction Video

No response

Environment

No response

Validations
  • Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
  • Check that this is a concrete bug. For Q&A, please ask on our Discord server instead.
  • This issue is valid
Contributions
  • I am willing to submit a PR to fix this issue
  • I am willing to submit a PR with failing tests (actually just go ahead and do it, thanks!)
Dominant language
TypeScript
Stars
39.3k
Forks
2.2k
Avg merge
9h 14m
Merged PRs (30d)
16

Getting set up

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 RSSNext/Folo

All issues in RSSNext/Folo

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.