Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

Stale activeGroupOid after group removal interrupts chat in legacy and React V2

未关闭
  • 哪里不对？
#1,816 0 条评论 0 个 reaction 已指派 1 人 在 GitHub 查看

维护者通常 1 天内回复

@paullizer 已经在做这个了。

开始于 2026年10月21日。

评估

这个 Issue 还没有评估数据。

描述

bug P1

Issue

A user removed from their active SimpleChat group retained that group's ID in settings.activeGroupOid. Sending messages repeatedly failed before Semantic Kernel initialization returned, leaving chat unusable. The reported user belonged to no other groups and could not readily choose another active group. Manually setting the persisted active-group value to JSON null restored chat.

The fix must cover both the legacy and React V2 chat experiences and must not require the user to repair their settings or belong to a group to use ordinary chat.

Steps to Reproduce

  1. Add a user to a SimpleChat group and select it as their active group.
  2. Configure an agent selection that enters per-user Semantic Kernel loading.
  3. Remove the user from that group, leaving the stored activeGroupOid unchanged. Include the case where the user has no other group memberships.
  4. Send an ordinary chat message using the legacy UI or React V2.
  5. Repeat after refreshing the page and within an already-open chat session.

Expected Behavior

  • A missing group or confirmed loss of membership invalidates the saved active-group preference without breaking otherwise-authorized chat.
  • Clear the confirmed stale preference to JSON null; do not automatically select another group or silently redirect a group-scoped operation into a different group.
  • Personal/global agent or model-only chat remains usable with no active group and with zero group memberships, subject to existing feature and authorization rules.
  • Both legacy and React V2 represent the recovered no-group state consistently.
  • Former group agents, actions, documents, and group-scoped conversations remain inaccessible. Explicit unauthorized group requests must retain their authorization failure behavior.
  • Transient storage/authorization-service failures must not be mistaken for proof that membership was revoked or cause a valid selection to be erased.
  • Recovery must preserve unrelated settings and a concurrent newly selected active group.

Actual Behavior

The supplied screenshot shows “Stream interrupted before any content was received” and “Stream interrupted: Something went wrong while streaming the response. Please try again.” The user reported this on every message until an administrator manually cleared the stale setting.

Impact

Group membership changes can prevent a user from continuing unrelated work in SimpleChat. Users with no remaining groups have no practical replacement group to select. An administrator currently needs to repair persisted user settings.

Notes

  • Priority: P1, requested by paullizer.
  • Assignee: paullizer.
  • Estimated size: M (shared backend recovery, settings persistence, both UI bootstrap paths, and regression coverage).
  • Inspected application version: 0.261.370 on the React V2 development line.
  • Source inspection confirms that application/single_app/semantic_kernel_loader.py::load_user_semantic_kernel calls require_active_group during optional group-agent discovery but only catches ValueError (no active group). functions_group.py::assert_group_role instead raises PermissionError for revoked membership and LookupError for a deleted group, allowing these errors to abort otherwise-independent agent loading.
  • route_backend_groups.py::remove_member removes membership but does not clear the removed user's active-group preference.
  • route_backend_v2.py::_resolve_active_scope filters unauthorized group IDs from the returned UI scope but does not repair persisted settings. route_frontend_chats.py::chats reads the raw active group for legacy page state.
  • Proposed scope: lazy, shared recovery when stale state is encountered, covering existing stale records as well as future membership changes; no bulk migration or automatic replacement group.
  • Add regression coverage for removal/deletion, no active group, no remaining groups, valid memberships/roles, personal/global selections, unavailable group selections, authorization boundaries, transient failures, concurrent setting changes, streaming and non-streaming chat, and both UI bootstrap paths.
  • Implementation has not started; root-cause evidence is source inspection plus the reported manual workaround, not a reproduced production trace.
  • Duplicate searches for activeGroupOid, active-group issues, and group-removal chat failures did not identify an existing issue for this failure.
主要语言
Python
星标
157
派生
117
平均合并
3 小时 31 分钟
30 天内合并 PR
226

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

microsoft/simplechat 的其他 Issue

查看 microsoft/simplechat 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。