You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maka.apache.org by "xxww0098 (via GitHub)" <gi...@apache.org> on 2026/08/20 09:26:20 UTC
[I] fix(desktop): keep packaged 0.1.11 sessions usable after rate-limit errors [maka]
xxww0098 opened a new issue, #3302:
URL: https://github.com/apache/maka/issues/3302
## Summary
In the packaged macOS Desktop build, a model rate-limit error was followed by repeated Runtime Host session-observation failures. The session became effectively unusable: transcript/session observers ended before becoming ready, and regenerate requests were rejected as `session_busy`.
This appears related to, but distinct from, #2516. That issue covers semantic classification of provider usage limits; this report covers the Desktop/Runtime Host lifecycle and recovery after the error.
## Observed
The user-visible error was:
```text
操作失败
触发模型速率限制
```
During the same captured window, the main-process diagnostics recorded:
- MCP capability refresh/startup failures because native tools had invalid schemas:
- `mcp__memory__create_entities`
- `mcp__playwright__browser_close`
- Repeated `runtime-host-session-observer` subscription recovery due to `slow_consumer`
- Repeated `sessions:transcript:open` failures: `Transcript observation ended before it became ready`
- Repeated `sessions:listActiveInteractions` / `sessions:observe` failures: `Runtime Host Session observer closed while opening` and `Session observation ended before it became ready`
- Repeated regenerate failures: `RuntimeHostOperationError: Session already has an active or pending root Turn` (`operation: turn.regenerate`, `code: session_busy`)
## Environment
- Maka: 0.1.11
- Build: packaged
- Electron: 43.2.0
- Chrome: 150.0.7871.129
- Node: 24.18.0
- OS: macOS 25.6.0, arm64
- Locale: zh-CN
- Captured at: 2026-08-20 09:21:13 +0800
- Runtime Host: protocol v0, compatibility 25, state `ready`
## Expected
- A provider rate-limit error should leave the session in a recoverable state.
- Session/transcript observers should not fail merely because an observation subscription is recovering or closes during startup.
- Regenerate should either wait for/abort the pending root turn or return a stable user-facing state, rather than repeatedly surfacing `session_busy`.
- An invalid optional MCP tool schema should not make the Desktop Runtime Host capability refresh/startup fail globally; the invalid capability should be isolated and reported clearly.
## Reproduction clues
The report does not establish which observer error is the root cause. Please correlate the rate-limit path, slow-consumer recovery, observation readiness/cleanup, and root-turn state handling in the packaged Desktop build.
Full diagnostic details are available in the reporter's attached diagnostic report.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@maka.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@maka.apache.org
For additional commands, e-mail: commits-help@maka.apache.org
Re: [I] fix(desktop): keep packaged 0.1.11 sessions usable after rate-limit errors [maka]
Posted by "CxHsin (via GitHub)" <gi...@apache.org>.
CxHsin commented on issue #3302:
URL: https://github.com/apache/maka/issues/3302#issuecomment-5356819997
I would like to work on this issue.
I will first reproduce the packaged Desktop timeline and add regression
coverage for rate-limit terminal settlement, observer recovery, and
regenerate admission. Before changing root-turn cleanup, I will determine
whether session_busy represents a genuinely active Turn, a failed terminal
transition, or an incomplete Host replacement.
I plan to keep optional MCP schema isolation in a separate PR so each change
has a focused cause and verification boundary. Please assign the issue to me
if this scope looks appropriate.
This investigation and implementation plan were prepared with assistance
from Codex. I will remain the human contributor of record and review the
result before submission.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@maka.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@maka.apache.org
For additional commands, e-mail: commits-help@maka.apache.org
Re: [I] fix(desktop): keep packaged 0.1.11 sessions usable after rate-limit errors [maka]
Posted by "CxHsin (via GitHub)" <gi...@apache.org>.
CxHsin commented on issue #3302:
URL: https://github.com/apache/maka/issues/3302#issuecomment-5356759500
I would like to work on this issue.
I will first reproduce the packaged Desktop timeline and add regression
coverage for rate-limit terminal settlement, observer recovery, and
regenerate admission. Before changing root-turn cleanup, I will determine
whether session_busy represents a genuinely active Turn, a failed terminal
transition, or an incomplete Host replacement.
I plan to keep optional MCP schema isolation in a separate PR so each change
has a focused cause and verification boundary. Please assign the issue to me
if this scope looks appropriate.
This investigation and implementation plan were prepared with assistance
from Codex. I will remain the human contributor of record and review the
result before submission.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@maka.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@maka.apache.org
For additional commands, e-mail: commits-help@maka.apache.org