Skip to content

Server/SSE + event/db hardening (audit-v7 and wave B findings) #49979

Closed as not planned

Description

@AceRothstein71

Context

Part of the fork hardening series proposed in #48638 (branch session-diff-events). Tracker: #49565.

Problem

Server/SSE and event/db paths: audit-v7 findings across server + MCP tooling, event fanout and TUI/SDK desync risks, and general wave 7-11 hardening at the server boundary.

Change set (commit list)

Validation

  • Targeted suites/typechecks green on the integration branch; no regressions across the audit corpus.

Linked: PR #48638 · tracker #49565 · sibling tracking issues listed in a follow-up comment.

Activity

  1. AceRothstein71 commented on Sep 19, 2026

    @AceRothstein71
    Author

    Cross-links: sibling tracking issues #49974 (perf/runtime), #49975 (shell classifier H-L), #49976 (shell classifier M-P), #49977 (instance lifecycle), #49978 (MCP/schema), #49979 (server/SSE + event/db), #49980 (updater tooling). Integration PR: #48638. Original tracker: #49565.

  2. opencodejr commented on Oct 28, 2026

    @opencodejr

    Thanks for opening this. As written, the issue describes a set of commits on your fork ("audit-v7", "wave B server/SSE", and so on), but it doesn't describe a problem in OpenCode that we can look into or reproduce. We can't act on a commit list on its own.

    If you have hit a concrete problem in the server, SSE, event or database paths, could you describe it briefly, in your own words:

    • the OpenCode version (opencode --version), your OS and how you installed it
    • what you did: the steps, command or setup (for example, how many concurrent sessions or which client was connected)
    • what you expected, and what happened instead, with the exact error, logs or a screenshot
    • if it's a specific code defect, the file and function in dev and why its current behaviour is wrong

    If there are several unrelated problems, please open a separate issue for each, using the Bug Report template.

    You can reply here with the details or edit the issue. If you edit it, please also leave a comment saying you've updated it, so we know when you're done.

    Related issues, most closely related first:

  3. opencodejr commented on Oct 31, 2026

    @opencodejr

    Closing this for now, since we haven't heard back. The issue lists commits from the session-diff-events fork branch, but it doesn't describe a problem we can reproduce or check in dev, so there's nothing here we can act on yet.

    If you run into a concrete server, SSE, event or database problem in OpenCode, please open a new issue with the Bug Report template. Include the version (opencode --version), your OS, the steps you took, what you expected and what happened, and any errors or logs. If it's a specific code defect, name the file and function in dev. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions