| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
# Conflicts: # packages/app/src/utils/server-compat.test.ts # packages/app/src/utils/server-health.test.ts # packages/app/src/utils/server-health.ts
* dev: (118 commits) chore: generate feat(app): support current event transport (anomalyco#38464) chore: generate feat(app): add dual-server compatibility (anomalyco#38462) chore: update nix node_modules hashes chore(app): vendor v2 promise client (anomalyco#38467) chore: update nix node_modules hashes fix(provider): serialize Mistral prompt cache keys (anomalyco#38448) fix(provider): select prompt cache keys by SDK (anomalyco#38424) feat(go): add Hy3 to Go model lineup (anomalyco#38349) fix(provider): correct MiniMax M3 thinking variants (anomalyco#38330) fix(docs): correct Kimi K2.7 Code request limits (anomalyco#38248) fix(app): show running shell command (anomalyco#38080) fix(app): defer unavailable notification state (anomalyco#38186) zen: add security check chore: generate zen: add security check zen: add laguna-2-2.1 chore: generate fix(app): support nested slash command autocomplete (anomalyco#38097) ...
Upstream's event-transport rework (anomalyco#38464) dropped the client-side heartbeat watchdog from anomalyco#13973 while the server still emits server.heartbeat every 10s. Without it a silently dead connection (typical after Android/iOS background suspension) stalls the stream forever: no streaming, permission prompts never clear, sessions stay busy until app restart. Re-add the 15s no-event abort so the existing reconnect loop recovers; applies to both v1 and v2 transports.
| Back | FazBrowse Home | New Git URL |
Summary
Validation
Stack