Skip to content

🤝 docs(README): Introduction to New Partners - #1627

Merged
Calcium-Ion merged 2 commits into
mainfrom
feature/new-partner-intro
Aug 21, 2025
Merged

🤝 docs(README): Introduction to New Partners#1627
Calcium-Ion merged 2 commits into
mainfrom
feature/new-partner-intro

Conversation

@t0ng7u

@t0ng7u t0ng7u commented Aug 21, 2025

Copy link
Copy Markdown
Collaborator

Summary by CodeRabbit

  • Documentation
    • Added a “Trusted Partners/合作伙伴” section with sponsor logos and links.
    • Updated environment variable docs: STREAMING_TIMEOUT default increased to 300 seconds.
    • Rebranded web API docs from “One API” to “New API” and refreshed formatting (block quotes, updated headings).
    • Enhanced API tables by adding clear column headers (Method, Path, Auth, Description).
    • Standardized update date presentation for consistency.

@coderabbitai

coderabbitai Bot commented Aug 21, 2025

Copy link
Copy Markdown
Contributor

Walkthrough

Documentation updates: both READMEs add a partners/sponsors section and change STREAMING_TIMEOUT default from 120s to 300s; the web API doc updates product naming to “New API,” adjusts headings/formatting, and adds a header row to a user-operations table.

Changes

Cohort / File(s) Summary
Readme updates
README.md, README.en.md
Added partners/sponsors section with logos/links; updated Environment Variables section to set STREAMING_TIMEOUT default to 300s (from 120s).
Web API docs rename and formatting
docs/api/web_api.md
Renamed “One API” to “New API”; converted intro and update note to block quotes; added table header (方法/路径/鉴权/说明) to section 5.2 user operations.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

A bunny taps its docs with cheer,
New partners hop into the sphere.
Streams linger longer—three hundred ticks,
Names refreshed with tidy fixes.
With paws that proof and whiskers neat,
This merge is clean—and quite a treat! 🐇✨

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch feature/new-partner-intro

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

  • Visit our Status Page to check the current availability of CodeRabbit.
  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 4

🧹 Nitpick comments (12)
docs/api/web_api.md (5)

64-79: Add blank lines around tables and normalize table headers for consistency

  • Markdown lint MD058: tables should be surrounded by blank lines. Add a blank line before/after the table under 5.2.
  • Consider enforcing the same 4-column header across all “用户模块” subsections to improve scanability.
  ### 5.2 用户自身操作 (需登录)
+ 
 | 方法 | 路径 | 鉴权 | 说明 |
 |------|------|------|------|
 | GET | /api/user/self/groups | 用户 | 获取自己所在分组 |
@@
 | POST | /api/user/aff_transfer | 用户 | 推广额度转账 |
 | PUT | /api/user/setting | 用户 | 更新用户设置 |
+ 

31-33: Clarify “可匿名/用户” 鉴权标签 or align to legend

The legend defines 公开、用户、管理员、Root, but row “/api/pricing” uses “可匿名/用户”. Either:

  • Change to “公开” if truly public, or
  • Extend the legend to define “可匿名” and how it differs from 公开.

172-174: Fix table formatting in Section 13

Section 13 currently shows a single row without a header or separators. For consistency with other sections, add a header row and fence lines.

 ## 13. 分组
-| GET | /api/group/ | 管理员 | 获取全部分组列表 |
+| 方法 | 路径 | 鉴权 | 说明 |
+|------|------|------|------|
+| GET | /api/group/ | 管理员 | 获取全部分组列表 |

15-23: Surround all tables with blank lines to satisfy MD058 and improve readability

Multiple sections place a table immediately after a heading with no blank line. Insert one blank line before and after each table. This will also make GitHub rendering and external tooling more robust.

Also applies to: 24-33, 35-40, 42-53, 55-63, 80-90, 92-98, 100-104, 106-131, 133-142, 144-153, 155-165, 167-171, 175-180, 182-186, 188-194


197-197: Update the “更新日期” if this PR modifies content

Doc footer still shows 2025.07.17. If we’re publishing these edits now, update to 2025.08.21 (or remove the footer if dates are tracked via VCS/CI).

README.md (3)

43-46: Prefer Markdown headings over raw HTML for ToC and consistency

Switch

to Markdown to keep consistent styling and auto-generated ToC behavior.

-<h2>🤝 我们信任的合作伙伴</h2>
+## 🤝 我们信任的合作伙伴

47-61: Optional: Lazy-load large logo images

Adding loading="lazy" to reduces initial page weight for the partner grid.

-    src="./docs/images/cherry-studio.png" alt="Cherry Studio" height="120"
+    src="./docs/images/cherry-studio.png" alt="Cherry Studio" height="120" loading="lazy"

Repeat for the other four images in this block.


138-139: Normalize env var key formatting

Other bullets list the variable name only; this one embeds a value. Suggest making it consistent.

-- `ERROR_LOG_ENABLED=true`: 是否记录并显示错误日志,默认`false`
+- `ERROR_LOG_ENABLED`: 是否记录并显示错误日志,默认 `false`

README.en.md (4)

43-46: Prefer Markdown headings over raw HTML for ToC and consistency

Use Markdown heading instead of

.

-<h2>🤝 Trusted Partners</h2>
+## 🤝 Trusted Partners

45-45: Minor wording polish

“In no particular order” reads more naturally.

-<p align="center"><strong>No particular order</strong></p>
+<p align="center"><strong>In no particular order</strong></p>

47-61: Optional: Lazy-load large images in the partners block

Add loading="lazy" to reduce initial page load.

-    src="./docs/images/cherry-studio.png" alt="Cherry Studio" height="120"
+    src="./docs/images/cherry-studio.png" alt="Cherry Studio" height="120" loading="lazy"

Repeat for the remaining four images.


138-139: Normalize env var key formatting

Keep only the key name for consistency with the rest.

-- `ERROR_LOG_ENABLED=true`: Whether to record and display error logs, default is `false`
+- `ERROR_LOG_ENABLED`: Whether to record and display error logs, default is `false`

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

💡 Knowledge Base configuration:

  • MCP integration is disabled by default for public repositories
  • Jira integration is disabled by default for public repositories
  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 4d0037a and 7c058bf.

⛔ Files ignored due to path filters (5)
  • docs/images/aliyun.png is excluded by !**/*.png
  • docs/images/cherry-studio.png is excluded by !**/*.png
  • docs/images/io-net.png is excluded by !**/*.png
  • docs/images/pku.png is excluded by !**/*.png
  • docs/images/ucloud.png is excluded by !**/*.png
📒 Files selected for processing (3)
  • README.en.md (2 hunks)
  • README.md (2 hunks)
  • docs/api/web_api.md (3 hunks)
🧰 Additional context used
🪛 markdownlint-cli2 (0.17.2)
README.en.md

56-56: Tables should be surrounded by blank lines

(MD058, blanks-around-tables)

🔇 Additional comments (3)
docs/api/web_api.md (1)

1-3: Branding rename to “New API” looks good

Consistent rename in title and intro. No functional impact.

README.md (1)

47-61: Verify asset availability

Ensure the five local images exist at the paths used: docs/images/{cherry-studio.png,pku.png,ucloud.png,aliyun.png,io-net.png}. Broken logos in the README are noisy.

README.en.md (1)

47-61: Verify assets exist at referenced paths

Ensure the five local images under docs/images are present to avoid broken images on GitHub and package registries.

Comment thread README.en.md
Comment on lines +43 to +64
<h2>🤝 Trusted Partners</h2>
<p id="premium-sponsors">&nbsp;</p>
<p align="center"><strong>No particular order</strong></p>
<p align="center">
<a href="https://www.cherry-ai.com/" target=_blank><img
src="./docs/images/cherry-studio.png" alt="Cherry Studio" height="120"
/></a>
<a href="https://bda.pku.edu.cn/" target=_blank><img
src="./docs/images/pku.png" alt="Peking University" height="120"
/></a>
<a href="https://www.compshare.cn/?ytag=GPU_yy_gh_newapi" target=_blank><img
src="./docs/images/ucloud.png" alt="UCloud" height="120"
/></a>
<a href="https://www.aliyun.com/" target=_blank><img
src="./docs/images/aliyun.png" alt="Alibaba Cloud" height="120"
/></a>
<a href="https://io.net/" target=_blank><img
src="./docs/images/io-net.png" alt="IO.NET" height="120"
/></a>
</p>
<p>&nbsp;</p>

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Refactor suggestion

Harden external links opened in new tabs

Add rel="noopener noreferrer" and quote the target attribute.

-  <a href="https://www.cherry-ai.com/" target=_blank><img
+  <a href="https://www.cherry-ai.com/" target="_blank" rel="noopener noreferrer"><img
@@
-  <a href="https://bda.pku.edu.cn/" target=_blank><img
+  <a href="https://bda.pku.edu.cn/" target="_blank" rel="noopener noreferrer"><img
@@
-  <a href="https://www.compshare.cn/?ytag=GPU_yy_gh_newapi" target=_blank><img
+  <a href="https://www.compshare.cn/?ytag=GPU_yy_gh_newapi" target="_blank" rel="noopener noreferrer"><img
@@
-  <a href="https://www.aliyun.com/" target=_blank><img
+  <a href="https://www.aliyun.com/" target="_blank" rel="noopener noreferrer"><img
@@
-  <a href="https://io.net/" target=_blank><img
+  <a href="https://io.net/" target="_blank" rel="noopener noreferrer"><img
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
<h2>🤝 Trusted Partners</h2>
<p id="premium-sponsors">&nbsp;</p>
<p align="center"><strong>No particular order</strong></p>
<p align="center">
<a href="https://www.cherry-ai.com/" target=_blank><img
src="./docs/images/cherry-studio.png" alt="Cherry Studio" height="120"
/></a>
<a href="https://bda.pku.edu.cn/" target=_blank><img
src="./docs/images/pku.png" alt="Peking University" height="120"
/></a>
<a href="https://www.compshare.cn/?ytag=GPU_yy_gh_newapi" target=_blank><img
src="./docs/images/ucloud.png" alt="UCloud" height="120"
/></a>
<a href="https://www.aliyun.com/" target=_blank><img
src="./docs/images/aliyun.png" alt="Alibaba Cloud" height="120"
/></a>
<a href="https://io.net/" target=_blank><img
src="./docs/images/io-net.png" alt="IO.NET" height="120"
/></a>
</p>
<p>&nbsp;</p>
<h2>🤝 Trusted Partners</h2>
<p id="premium-sponsors">&nbsp;</p>
<p align="center"><strong>No particular order</strong></p>
<p align="center">
<a href="https://www.cherry-ai.com/" target="_blank" rel="noopener noreferrer"><img
src="./docs/images/cherry-studio.png" alt="Cherry Studio" height="120"
/></a>
<a href="https://bda.pku.edu.cn/" target="_blank" rel="noopener noreferrer"><img
src="./docs/images/pku.png" alt="Peking University" height="120"
/></a>
<a href="https://www.compshare.cn/?ytag=GPU_yy_gh_newapi" target="_blank" rel="noopener noreferrer"><img
src="./docs/images/ucloud.png" alt="UCloud" height="120"
/></a>
<a href="https://www.aliyun.com/" target="_blank" rel="noopener noreferrer"><img
src="./docs/images/aliyun.png" alt="Alibaba Cloud" height="120"
/></a>
<a href="https://io.net/" target="_blank" rel="noopener noreferrer"><img
src="./docs/images/io-net.png" alt="IO.NET" height="120"
/></a>
</p>
<p>&nbsp;</p>
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

56-56: Tables should be surrounded by blank lines

(MD058, blanks-around-tables)

🤖 Prompt for AI Agents
In README.en.md around lines 43 to 64, the external anchor tags use unquoted
target attributes and open in new tabs without rel protections; update each <a>
tag to use target="_blank" (quoted) and add rel="noopener noreferrer" to each
external link so they are hardened against reverse tabnabbing and comply with
best practices.

Comment thread README.en.md

- `GENERATE_DEFAULT_TOKEN`: Whether to generate initial tokens for newly registered users, default is `false`
- `STREAMING_TIMEOUT`: Streaming response timeout, default is 120 seconds
- `STREAMING_TIMEOUT`: Streaming response timeout, default is 300 seconds

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Verification agent

🧩 Analysis chain

STREAMING_TIMEOUT default to 300s — ensure implementation matches

Mirror of the zh-CN README note: verify code/config defaults and other docs.


🏁 Script executed:

#!/bin/bash
# Same audit as in README.md; kept separate in case this file lives in a submodule/website.
set -euo pipefail
rg -nP --hidden --no-ignore 'STREAMING_TIMEOUT\s*[:=]\s*["'\'']?\d+["'\'']?' -S -g '!**/node_modules/**' -g '!**/dist/**' -g '!**/build/**'
rg -nP --hidden --no-ignore 'STREAMING_TIMEOUT[^\\n]{0,80}120' -S -g '!**/node_modules/**' -g '!**/dist/**' -g '!**/build/**'

Length of output: 657


STREAMING_TIMEOUT default mismatch — documentation update required

The codebase defines the default STREAMING_TIMEOUT as 120 seconds (see common/init.go:104), and both the example in docker-compose.yml and .env.example comment likewise reference 120 seconds. Please update the English README (and mirror the change in the Chinese version) so that line 125 reads:

- `STREAMING_TIMEOUT`: Streaming response timeout, default is 300 seconds
+ `STREAMING_TIMEOUT`: Streaming response timeout, default is 120 seconds
🤖 Prompt for AI Agents
In README.en.md around line 125, the documented default for STREAMING_TIMEOUT is
incorrect (says 300 seconds); update that line to state the default is 120
seconds (replace "300 seconds" with "120 seconds"); also apply the same change
to the Chinese README (README.zh.md or equivalent) so both docs match the code
and examples.

Comment thread README.md
Comment on lines +43 to +64
<h2>🤝 我们信任的合作伙伴</h2>
<p id="premium-sponsors">&nbsp;</p>
<p align="center"><strong>排名不分先后</strong></p>
<p align="center">
<a href="https://www.cherry-ai.com/" target=_blank><img
src="./docs/images/cherry-studio.png" alt="Cherry Studio" height="120"
/></a>
<a href="https://bda.pku.edu.cn/" target=_blank><img
src="./docs/images/pku.png" alt="北京大学" height="120"
/></a>
<a href="https://www.compshare.cn/?ytag=GPU_yy_gh_newapi" target=_blank><img
src="./docs/images/ucloud.png" alt="UCloud 优刻得" height="120"
/></a>
<a href="https://www.aliyun.com/" target=_blank><img
src="./docs/images/aliyun.png" alt="阿里云" height="120"
/></a>
<a href="https://io.net/" target=_blank><img
src="./docs/images/io-net.png" alt="IO.NET" height="120"
/></a>
</p>
<p>&nbsp;</p>

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Refactor suggestion

Harden external links opened in new tabs

Add rel="noopener noreferrer" and quote the target attribute to prevent reverse tabnabbing and improve HTML validity.

-  <a href="https://www.cherry-ai.com/" target=_blank><img
+  <a href="https://www.cherry-ai.com/" target="_blank" rel="noopener noreferrer"><img
@@
-  <a href="https://bda.pku.edu.cn/" target=_blank><img
+  <a href="https://bda.pku.edu.cn/" target="_blank" rel="noopener noreferrer"><img
@@
-  <a href="https://www.compshare.cn/?ytag=GPU_yy_gh_newapi" target=_blank><img
+  <a href="https://www.compshare.cn/?ytag=GPU_yy_gh_newapi" target="_blank" rel="noopener noreferrer"><img
@@
-  <a href="https://www.aliyun.com/" target=_blank><img
+  <a href="https://www.aliyun.com/" target="_blank" rel="noopener noreferrer"><img
@@
-  <a href="https://io.net/" target=_blank><img
+  <a href="https://io.net/" target="_blank" rel="noopener noreferrer"><img
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
<h2>🤝 我们信任的合作伙伴</h2>
<p id="premium-sponsors">&nbsp;</p>
<p align="center"><strong>排名不分先后</strong></p>
<p align="center">
<a href="https://www.cherry-ai.com/" target=_blank><img
src="./docs/images/cherry-studio.png" alt="Cherry Studio" height="120"
/></a>
<a href="https://bda.pku.edu.cn/" target=_blank><img
src="./docs/images/pku.png" alt="北京大学" height="120"
/></a>
<a href="https://www.compshare.cn/?ytag=GPU_yy_gh_newapi" target=_blank><img
src="./docs/images/ucloud.png" alt="UCloud 优刻得" height="120"
/></a>
<a href="https://www.aliyun.com/" target=_blank><img
src="./docs/images/aliyun.png" alt="阿里云" height="120"
/></a>
<a href="https://io.net/" target=_blank><img
src="./docs/images/io-net.png" alt="IO.NET" height="120"
/></a>
</p>
<p>&nbsp;</p>
<h2>🤝 我们信任的合作伙伴</h2>
<p id="premium-sponsors">&nbsp;</p>
<p align="center"><strong>排名不分先后</strong></p>
<p align="center">
<a href="https://www.cherry-ai.com/" target="_blank" rel="noopener noreferrer"><img
src="./docs/images/cherry-studio.png" alt="Cherry Studio" height="120"
/></a>
<a href="https://bda.pku.edu.cn/" target="_blank" rel="noopener noreferrer"><img
src="./docs/images/pku.png" alt="北京大学" height="120"
/></a>
<a href="https://www.compshare.cn/?ytag=GPU_yy_gh_newapi" target="_blank" rel="noopener noreferrer"><img
src="./docs/images/ucloud.png" alt="UCloud 优刻得" height="120"
/></a>
<a href="https://www.aliyun.com/" target="_blank" rel="noopener noreferrer"><img
src="./docs/images/aliyun.png" alt="阿里云" height="120"
/></a>
<a href="https://io.net/" target="_blank" rel="noopener noreferrer"><img
src="./docs/images/io-net.png" alt="IO.NET" height="120"
/></a>
</p>
<p>&nbsp;</p>
🤖 Prompt for AI Agents
In README.md around lines 43 to 64, the anchor tags open external links in new
tabs using unquoted target attributes and lack rel protections; update each <a>
tag in this block to quote the target attribute (target="_blank") and add
rel="noopener noreferrer" to prevent reverse tabnabbing and satisfy HTML
validity; ensure all anchors in the shown partner/logo section are updated
consistently.

Comment thread README.md

- `GENERATE_DEFAULT_TOKEN`:是否为新注册用户生成初始令牌,默认为 `false`
- `STREAMING_TIMEOUT`:流式回复超时时间,默认120秒
- `STREAMING_TIMEOUT`:流式回复超时时间,默认300秒

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Verification agent

🧩 Analysis chain

STREAMING_TIMEOUT default changed to 300s — verify implementation and other docs

Nice doc update. Please confirm the actual default in code/config matches 300s (env loaders, Helm charts, Docker examples, .env templates). If not, either update code or revert docs.


🏁 Script executed:

#!/bin/bash
# Verify STREAMING_TIMEOUT defaults and docs consistency.

set -euo pipefail

echo "Search occurrences of STREAMING_TIMEOUT with numeric defaults:"
rg -nP --hidden --no-ignore 'STREAMING_TIMEOUT\s*[:=]\s*["'\'']?\d+["'\'']?' -S -g '!**/node_modules/**' -g '!**/dist/**' -g '!**/build/**'

echo
echo "Check for any lingering 120-second mentions tied to STREAMING_TIMEOUT:"
rg -nP --hidden --no-ignore 'STREAMING_TIMEOUT[^\\n]{0,80}120' -S -g '!**/node_modules/**' -g '!**/dist/**' -g '!**/build/**'

echo
echo "Common config files that might carry defaults:"
fd -H -t f -i '(.env|.env.example|docker-compose.*|values.*\.ya?ml|Chart\.ya?ml|kustomization\.ya?ml|config\.(ya?ml|json)|settings\.(ya?ml|json))' \
  -E node_modules -E dist -E build | sed -n '1,200p'

echo
echo "Show lines around STREAMING_TIMEOUT in config-like files:"
fd -H -t f -i '(.env|.env.example|docker-compose.*|values.*\.ya?ml|Chart\.ya?ml|kustomization\.ya?ml|config\.(ya?ml|json)|settings\.(ya?ml|json))' \
  -E node_modules -E dist -E build \
  | xargs -r rg -nP 'STREAMING_TIMEOUT.*' -S -n -C2

Length of output: 2282


Mismatch between documented and actual STREAMING_TIMEOUT default

The documentation now states a 300-second default, but the code and example configurations still use 120 seconds. Please align them by updating the implementation and examples (or revert the docs if 120s is intended).

Files requiring updates:

  • common/init.go (around line 104):
    - constant.StreamingTimeout = GetEnvOrDefault("STREAMING_TIMEOUT", 120)
    + constant.StreamingTimeout = GetEnvOrDefault("STREAMING_TIMEOUT", 300)
  • .env.example (line 50):
    - # STREAMING_TIMEOUT=120
    + # STREAMING_TIMEOUT=300
  • docker-compose.yml (line 19):
    - #      - STREAMING_TIMEOUT=120  # 流模式无响应超时时间,单位秒,默认120秒,如果出现空补全可以尝试改为更大值
    + #      - STREAMING_TIMEOUT=300  # 流模式无响应超时时间,单位秒,默认300秒,如果出现空补全可以尝试改为更大值
🤖 Prompt for AI Agents
In README.md line 125 and in the codebase (common/init.go around line 104,
.env.example line 50, docker-compose.yml line 19) the documented
STREAMING_TIMEOUT (300s) mismatches actual defaults (120s); align them by
updating the implementation and examples to 300s: change the default/constant in
common/init.go to 300 (or read from env with fallback 300), set
STREAMING_TIMEOUT=300 in .env.example, and set the environment variable value to
300 in docker-compose.yml; also search the repo for other STREAMING_TIMEOUT
occurrences and update any remaining examples or defaults to 300 (or revert
README to 120 if 120s is the intended value).

@Calcium-Ion
Calcium-Ion merged commit c826d06 into main Aug 21, 2025
1 of 3 checks passed
@Calcium-Ion
Calcium-Ion deleted the feature/new-partner-intro branch October 11, 2025 03:06
x22x22 pushed a commit to x22x22/new-api that referenced this pull request Apr 24, 2026
…ner-intro

🤝 docs(README): Introduction to New Partners
@coderabbitai coderabbitai Bot mentioned this pull request May 21, 2026
11 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants