mttu-developers/konabot
8
2
Fork 3
Code Issues 13 Pull Requests 1 Actions Packages Releases 79 Activity

Enhancement: 为 man 和 textfx 指令添加图片渲染和文本 fallback #54

Merged
Passthem merged 4 commits from enhancement/man-and-textfx into master 2026-02-25 16:26:13 +08:00
Conversation 4 Commits 4 Files Changed 4 +51 -10
Passthem commented 2026-02-25 16:12:23 +08:00
Owner
Copy Link

PR Type

Enhancement, Bug fix

Description

  • 新增错误消息渲染为图片的通用模块

  • textfx 指令错误输出改用图片渲染

  • man 指令添加图片渲染失败的文本 fallback

  • 修复 core.py 文件末尾缺少换行符

Diagram Walkthrough

flowchart LR
  A["render_error_message 模块"] -- "渲染错误图片" --> B["textfx 错误处理"]
  A -- "渲染失败回退文本" --> B
  C["man 指令"] -- "Markdown 渲染失败" --> D["文本 fallback"]

File Walkthrough
Relevant files
Enhancement
render_error_message.py
新增错误消息图片渲染通用模块                                                                                     

konabot/common/render_error_message.py

  • 新增 render_error_message 函数，将错误文本渲染为图片
  • 使用 Playwright 调用 Web 端 error_report 页面进行渲染
  • 渲染失败时捕获异常并回退为纯文本消息
 +34/-0   
__init__.py
textfx 错误输出改用图片渲染                                                                               

konabot/plugins/handle_text/init.py

  • 管道执行出错时调用 render_error_message 渲染错误信息为图片
  • 替换原有的纯文本错误消息发送逻辑
 +4/-1     
Error handling
__init__.py
man 指令添加渲染失败文本 fallback                                                                   

konabot/plugins/man/init.py

  • 为 Markdown 图片渲染添加 try-except 异常捕获
  • 捕获 playwright.async_api.Error 和 ConnectionError 后回退发送纯文本
 +8/-3     
Formatting
core.py
修复文件末尾缺少换行符                                                                                           

konabot/plugins/markdown/core.py

  • 修复文件末尾缺少换行符的问题
 +5/-6     
### **PR Type** Enhancement, Bug fix ___ ### **Description** - 新增错误消息渲染为图片的通用模块 - textfx 指令错误输出改用图片渲染 - man 指令添加图片渲染失败的文本 fallback - 修复 `core.py` 文件末尾缺少换行符 ___ ### Diagram Walkthrough ```mermaid flowchart LR A["render_error_message 模块"] -- "渲染错误图片" --> B["textfx 错误处理"] A -- "渲染失败回退文本" --> B C["man 指令"] -- "Markdown 渲染失败" --> D["文本 fallback"] ``` <details> <summary><h3> File Walkthrough</h3></summary> <table><thead><tr><th></th><th align="left">Relevant files</th></tr></thead><tbody><tr><td><strong>Enhancement</strong></td><td><table> <tr> <td> <details> <summary><strong>render_error_message.py</strong><dd><code>新增错误消息图片渲染通用模块</code>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; </dd></summary> <hr> konabot/common/render_error_message.py <ul><li>新增 <code>render_error_message</code> 函数，将错误文本渲染为图片<br> <li> 使用 Playwright 调用 Web 端 <code>error_report</code> 页面进行渲染<br> <li> 渲染失败时捕获异常并回退为纯文本消息</ul> </details> </td> <td><a href="https://gitea.service.jazzwhom.top/mttu-developers/konabot/src/branch/enhancement/man-and-textfx/konabot/common/render_error_message.py">+34/-0</a>&nbsp; &nbsp; </td> </tr> <tr> <td> <details> <summary><strong>__init__.py</strong><dd><code>textfx 错误输出改用图片渲染</code>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; </dd></summary> <hr> konabot/plugins/handle_text/__init__.py - 管道执行出错时调用 `render_error_message` 渲染错误信息为图片 - 替换原有的纯文本错误消息发送逻辑 </details> </td> <td><a href="https://gitea.service.jazzwhom.top/mttu-developers/konabot/src/branch/enhancement/man-and-textfx/konabot/plugins/handle_text/__init__.py">+4/-1</a>&nbsp; &nbsp; &nbsp; </td> </tr> </table></td></tr><tr><td><strong>Error handling</strong></td><td><table> <tr> <td> <details> <summary><strong>__init__.py</strong><dd><code>man 指令添加渲染失败文本 fallback</code>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; </dd></summary> <hr> konabot/plugins/man/__init__.py <ul><li>为 Markdown 图片渲染添加 try-except 异常捕获<br> <li> 捕获 <code>playwright.async_api.Error</code> 和 <code>ConnectionError</code> 后回退发送纯文本</ul> </details> </td> <td><a href="https://gitea.service.jazzwhom.top/mttu-developers/konabot/src/branch/enhancement/man-and-textfx/konabot/plugins/man/__init__.py">+8/-3</a>&nbsp; &nbsp; &nbsp; </td> </tr> </table></td></tr><tr><td><strong>Formatting</strong></td><td><table> <tr> <td> <details> <summary><strong>core.py</strong><dd><code>修复文件末尾缺少换行符</code>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; </dd></summary> <hr> konabot/plugins/markdown/core.py - 修复文件末尾缺少换行符的问题 </details> </td> <td><a href="https://gitea.service.jazzwhom.top/mttu-developers/konabot/src/branch/enhancement/man-and-textfx/konabot/plugins/markdown/core.py">+5/-6</a>&nbsp; &nbsp; &nbsp; </td> </tr> </table></td></tr></tr></tbody></table> </details> ___
Passthem added 2 commits 2026-02-25 16:12:23 +08:00
添加 man 指令的渲染 Fallback 27841b8422
添加渲染错误信息为图片 91769f93ae
kagami-review commented 2026-02-25 16:12:56 +08:00
Collaborator
Copy Link

PR Reviewer Guide 🔍

(Review updated until commit 9c9496efbd)

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 2 🔵🔵⚪⚪⚪
🧪 No relevant tests
🔒 Security concerns

潜在 XSS 风险：在 render_error_message.py 中，用户可控的 r.ostream 内容被拼接进 message 后，通过 page.evaluate 传递给前端的 setContent 函数。如果该前端函数使用 innerHTML 等不安全方式渲染内容，攻击者可能通过构造恶意输入实现脚本注入。建议确认前端 setContent 实现中是否对输入进行了适当的 HTML 转义。

⚡ Recommended focus areas for review

错误遍历逻辑

当多个 results 中存在多个错误时，循环只会渲染并发送第一个错误就 return，后续错误会被静默忽略。应确认这是否是预期行为，或者是否需要汇总所有错误后一并展示给用户。

 
if r.code != 0:
    message = f"处理指令时出现问题：{r.ostream}"
    rendered = await render_error_message(message)
    await target.send_message(rendered)
    return
XSS 风险

message 字符串通过 page.evaluate 直接传入前端 setContent 函数。如果 message 包含用户可控内容（如 r.ostream），且 setContent 内部使用 innerHTML 等方式渲染，则可能存在注入风险。应确认前端侧是否对输入做了转义处理。

 
await page.evaluate(
    """(message) => {return setContent(message);}""",
    message,
)
## PR Reviewer Guide 🔍 #### (Review updated until commit https://gitea.service.jazzwhom.top/mttu-developers/konabot/commit/9c9496efbd5e5db63e0fdb51970afc79372218ea) Here are some key observations to aid the review process: <table> <tr><td>⏱️&nbsp;<strong>Estimated effort to review</strong>: 2 🔵🔵⚪⚪⚪</td></tr> <tr><td>🧪&nbsp;<strong>No relevant tests</strong></td></tr> <tr><td>🔒&nbsp;<strong>Security concerns</strong><br><br> 潜在 XSS 风险：在 `render_error_message.py` 中，用户可控的 `r.ostream` 内容被拼接进 `message` 后，通过 `page.evaluate` 传递给前端的 `setContent` 函数。如果该前端函数使用 `innerHTML` 等不安全方式渲染内容，攻击者可能通过构造恶意输入实现脚本注入。建议确认前端 `setContent` 实现中是否对输入进行了适当的 HTML 转义。</td></tr> <tr><td>⚡&nbsp;<strong>Recommended focus areas for review</strong><br><br> <details><summary><a href='https://gitea.service.jazzwhom.top/mttu-developers/konabot/src/branch/enhancement/man-and-textfx/konabot/plugins/handle_text/__init__.py#L78-L82'><strong>错误遍历逻辑</strong></a> 当多个 `results` 中存在多个错误时，循环只会渲染并发送第一个错误就 `return`，后续错误会被静默忽略。应确认这是否是预期行为，或者是否需要汇总所有错误后一并展示给用户。 </summary> ```python if r.code != 0: message = f"处理指令时出现问题：{r.ostream}" rendered = await render_error_message(message) await target.send_message(rendered) return ``` </details> <details><summary><a href='https://gitea.service.jazzwhom.top/mttu-developers/konabot/src/branch/enhancement/man-and-textfx/konabot/common/render_error_message.py#L19-L22'><strong>XSS 风险</strong></a> `message` 字符串通过 `page.evaluate` 直接传入前端 `setContent` 函数。如果 `message` 包含用户可控内容（如 `r.ostream`），且 `setContent` 内部使用 `innerHTML` 等方式渲染，则可能存在注入风险。应确认前端侧是否对输入做了转义处理。 </summary> ```python await page.evaluate( """(message) => {return setContent(message);}""", message, ) ``` </details> </td></tr> </table>
kagami-review commented 2026-02-25 16:13:16 +08:00
Collaborator
Copy Link

PR Code Suggestions ✨

Latest suggestions up to 9c9496e

Explore these optional code suggestions:

CategorySuggestion                                                                                                                                    Impact
General
页面加载超时时间可能过短

render 方法内部可能也有自己的超时设置，但这里 wait_for_function 的 3 秒超时如果触发，会抛出
playwright.async_api.TimeoutError（它是 playwright.async_api.Error 的子类），虽然外层能捕获，但 3
秒对于页面加载来说可能偏短，容易导致频繁 fallback。建议适当增大超时时间或使其可配置。

konabot/common/render_error_message.py [18]

-await page.wait_for_function("typeof setContent === 'function'", timeout=3000)
+await page.wait_for_function("typeof setContent === 'function'", timeout=10000)
Suggestion importance[1-10]: 3

__

Why: The suggestion is technically valid — 3 seconds could be tight for page load in some environments, and the TimeoutError would indeed be caught by the outer except. However, this is a minor tuning concern rather than a bug. The current 3-second timeout is a reasonable default for a simple error rendering page, and the fallback to plain text already handles the timeout gracefully. The impact is low.

Low

Previous suggestions

Suggestions up to commit 9c9496e
CategorySuggestion                                                                                                                                    Impact
General
页面函数等待超时时间过短

timeout=1000 仅为 1 秒，在高负载或冷启动场景下，页面 JS 函数可能尚未就绪就会超时，导致频繁回退到纯文本。建议适当增大超时时间（如
5000ms），以提高渲染成功率。

konabot/common/render_error_message.py [18]

-await page.wait_for_function("typeof setContent === 'function'", timeout=1000)
+await page.wait_for_function("typeof setContent === 'function'", timeout=5000)
Suggestion importance[1-10]: 4

__

Why: The suggestion is reasonable — a 1-second timeout could be tight under cold start or high load. However, this is a minor tuning concern rather than a bug. The function already has a fallback to plain text on failure (line 31-33), so a timeout here gracefully degrades. The impact is low since the fallback behavior is already handled correctly.

Low
Suggestions up to commit 7026337
CategorySuggestion                                                                                                                                    Impact
Possible issue
Fallback 异常捕获范围过窄

当前只捕获了 playwright.async_api.Error，但渲染过程中也可能抛出其他异常（如网络超时、连接被拒绝等非 Playwright
特定异常），这会导致未被捕获的异常向上传播，用户收不到任何反馈。建议捕获更宽泛的 Exception 以确保文本 fallback 始终生效。

konabot/common/render_error_message.py [31-33]

-except playwright.async_api.Error as e:
+except Exception as e:
     logger.warning(f"渲染报错信息图片时出错了，回退到文本 ERR={e}")
     return UniMessage.text(message)
Suggestion importance[1-10]: 6

__

Why: The suggestion is valid — playwright.async_api.Error won't catch all possible failures during rendering (e.g., ConnectionError, asyncio.TimeoutError). Broadening to Exception ensures the text fallback always works. However, this is a moderate error-handling improvement rather than a critical bug, since the most likely failures in a Playwright rendering path are indeed Playwright errors.

Low
Man 指令 fallback 异常捕获过窄

与 render_error_message 同理，MarkDownCore.render_markdown 可能抛出非
playwright.async_api.Error 的异常（如连接错误、超时等），导致 fallback 逻辑不会触发，用户看到的是未处理的错误。建议捕获更宽泛的
Exception 并记录日志。

konabot/plugins/man/init.py [102-104]

-except playwright.async_api.Error:
+except Exception as e:
     # 图片渲染出错，改成发纯文本
+    logger.warning(f"渲染 man 文档图片时出错，回退到文本 ERR={e}")
     await man.send(UniMessage.text(mans_msg))
Suggestion importance[1-10]: 6

__

Why: Same reasoning as suggestion 1 — catching only playwright.async_api.Error may miss non-Playwright exceptions, leaving the user with no response. Adding logging is also a good practice. It's a reasonable improvement but not critical, as the primary failure mode is likely a Playwright error.

Low
## PR Code Suggestions ✨ <!-- 9c9496e --> Latest suggestions up to 9c9496e Explore these optional code suggestions: <table><thead><tr><td><strong>Category</strong></td><td align=left><strong>Suggestion&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; </strong></td><td align=center><strong>Impact</strong></td></tr><tbody><tr><td rowspan=1>General</td> <td> <details><summary>页面加载超时时间可能过短</summary> ___ **<code>render</code> 方法内部可能也有自己的超时设置，但这里 <code>wait_for_function</code> 的 3 秒超时如果触发，会抛出 <br><code>playwright.async_api.TimeoutError</code>（它是 <code>playwright.async_api.Error</code> 的子类），虽然外层能捕获，但 3 <br>秒对于页面加载来说可能偏短，容易导致频繁 fallback。建议适当增大超时时间或使其可配置。** [konabot/common/render_error_message.py [18]](https://gitea.service.jazzwhom.top/mttu-developers/konabot/src/branch/enhancement/man-and-textfx/konabot/common/render_error_message.py#L18-L18) ```diff -await page.wait_for_function("typeof setContent === 'function'", timeout=3000) +await page.wait_for_function("typeof setContent === 'function'", timeout=10000) ``` <details><summary>Suggestion importance[1-10]: 3</summary> __ Why: The suggestion is technically valid — 3 seconds could be tight for page load in some environments, and the `TimeoutError` would indeed be caught by the outer `except`. However, this is a minor tuning concern rather than a bug. The current 3-second timeout is a reasonable default for a simple error rendering page, and the fallback to plain text already handles the timeout gracefully. The impact is low. </details></details></td><td align=center>Low </td></tr></tr></tbody></table> ___ #### Previous suggestions <details><summary>Suggestions up to commit 9c9496e</summary> <br><table><thead><tr><td><strong>Category</strong></td><td align=left><strong>Suggestion&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; </strong></td><td align=center><strong>Impact</strong></td></tr><tbody><tr><td rowspan=1>General</td> <td> <details><summary>页面函数等待超时时间过短</summary> ___ **<code>timeout=1000</code> 仅为 1 秒，在高负载或冷启动场景下，页面 JS 函数可能尚未就绪就会超时，导致频繁回退到纯文本。建议适当增大超时时间（如 <br>5000ms），以提高渲染成功率。** [konabot/common/render_error_message.py [18]](https://gitea.service.jazzwhom.top/mttu-developers/konabot/src/branch/enhancement/man-and-textfx/konabot/common/render_error_message.py#L18-L18) ```diff -await page.wait_for_function("typeof setContent === 'function'", timeout=1000) +await page.wait_for_function("typeof setContent === 'function'", timeout=5000) ``` <details><summary>Suggestion importance[1-10]: 4</summary> __ Why: The suggestion is reasonable — a 1-second timeout could be tight under cold start or high load. However, this is a minor tuning concern rather than a bug. The function already has a fallback to plain text on failure (line 31-33), so a timeout here gracefully degrades. The impact is low since the fallback behavior is already handled correctly. </details></details></td><td align=center>Low </td></tr></tr></tbody></table> </details> <details><summary>Suggestions up to commit 7026337</summary> <br><table><thead><tr><td><strong>Category</strong></td><td align=left><strong>Suggestion&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; </strong></td><td align=center><strong>Impact</strong></td></tr><tbody><tr><td rowspan=2>Possible issue</td> <td> <details><summary>Fallback 异常捕获范围过窄</summary> ___ **当前只捕获了 <code>playwright.async_api.Error</code>，但渲染过程中也可能抛出其他异常（如网络超时、连接被拒绝等非 Playwright <br>特定异常），这会导致未被捕获的异常向上传播，用户收不到任何反馈。建议捕获更宽泛的 <code>Exception</code> 以确保文本 fallback 始终生效。** [konabot/common/render_error_message.py [31-33]](https://gitea.service.jazzwhom.top/mttu-developers/konabot/src/branch/enhancement/man-and-textfx/konabot/common/render_error_message.py#L31-L33) ```diff -except playwright.async_api.Error as e: +except Exception as e: logger.warning(f"渲染报错信息图片时出错了，回退到文本 ERR={e}") return UniMessage.text(message) ``` <details><summary>Suggestion importance[1-10]: 6</summary> __ Why: The suggestion is valid — `playwright.async_api.Error` won't catch all possible failures during rendering (e.g., `ConnectionError`, `asyncio.TimeoutError`). Broadening to `Exception` ensures the text fallback always works. However, this is a moderate error-handling improvement rather than a critical bug, since the most likely failures in a Playwright rendering path are indeed Playwright errors. </details></details></td><td align=center>Low </td></tr><tr><td> <details><summary>Man 指令 fallback 异常捕获过窄</summary> ___ **与 <code>render_error_message</code> 同理，<code>MarkDownCore.render_markdown</code> 可能抛出非 <br><code>playwright.async_api.Error</code> 的异常（如连接错误、超时等），导致 fallback 逻辑不会触发，用户看到的是未处理的错误。建议捕获更宽泛的 <br><code>Exception</code> 并记录日志。** [konabot/plugins/man/__init__.py [102-104]](https://gitea.service.jazzwhom.top/mttu-developers/konabot/src/branch/enhancement/man-and-textfx/konabot/plugins/man/__init__.py#L102-L104) ```diff -except playwright.async_api.Error: +except Exception as e: # 图片渲染出错，改成发纯文本 + logger.warning(f"渲染 man 文档图片时出错，回退到文本 ERR={e}") await man.send(UniMessage.text(mans_msg)) ``` <details><summary>Suggestion importance[1-10]: 6</summary> __ Why: Same reasoning as suggestion 1 — catching only `playwright.async_api.Error` may miss non-Playwright exceptions, leaving the user with no response. Adding logging is also a good practice. It's a reasonable improvement but not critical, as the primary failure mode is likely a Playwright error. </details></details></td><td align=center>Low </td></tr></tr></tbody></table> </details>
Passthem added 1 commit 2026-02-25 16:20:48 +08:00
添加错误捕获范围，调整日志注入参数方式 34175e8c17
kagami-review commented 2026-02-25 16:21:25 +08:00
Collaborator
Copy Link

Persistent review updated to latest commit 9c9496efbd

**[Persistent review](https://gitea.service.jazzwhom.top/mttu-developers/konabot/pulls/54#issuecomment-283)** updated to latest commit https://gitea.service.jazzwhom.top/mttu-developers/konabot/commit/9c9496efbd5e5db63e0fdb51970afc79372218ea
Passthem added 1 commit 2026-02-25 16:24:23 +08:00
把 timeout 调长一点 df409a13a9
kagami-review commented 2026-02-25 16:24:57 +08:00
Collaborator
Copy Link

Persistent review updated to latest commit 9c9496efbd

**[Persistent review](https://gitea.service.jazzwhom.top/mttu-developers/konabot/pulls/54#issuecomment-283)** updated to latest commit https://gitea.service.jazzwhom.top/mttu-developers/konabot/commit/9c9496efbd5e5db63e0fdb51970afc79372218ea
Passthem merged commit 94db34037b into master 2026-02-25 16:26:13 +08:00
Passthem deleted branch enhancement/man-and-textfx 2026-02-25 16:26:13 +08:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
Compat/Breaking
Breaking change that won't be backward compatible
Kind/Bug
Something is not working
Kind/Documentation
Documentation changes
Kind/Enhancement
Improve existing functionality
Kind/Feature
New functionality
Kind/Security
This is security issue
Kind/Testing
Issue or pull request related to testing
Priority
Critical
1
The priority is critical
Priority
High
2
The priority is high
Priority
Low
4
The priority is low
Priority
Medium
3
The priority is medium
Reviewed
Confirmed
1
Issue has been confirmed
Reviewed
Duplicate
2
This issue or pull request already exists
Reviewed
Invalid
3
Invalid issue
Reviewed
Won't Fix
3
This issue won't be fixed
Status
Abandoned
3
Somebody has started to work on this but abandoned work
Status
Blocked
1
Something is blocking this issue or pull request
Status
Need More Info
2
Feedback is required to reproduce issue or to continue work
No Label
Milestone
No items
No Milestone
Assignees
Clear assignees
MixBadGun Omega98 Passthem asynkio kagami-ci kagami-review tnot wzq02
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: mttu-developers/konabot#54
No description provided.
Delete Branch "enhancement/man-and-textfx"

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?