Skip to content

[Gastown] Kilo Code Review check persistently fails: "Could not connect to the sandbox" (recurring across PRs) #4295

Closed as not planned

Description

@kilo-code-bot

What happened?

The "Kilo Code Review" GitHub check (app.kilo.ai) persistently fails with a sandbox connectivity error on multiple PRs in the ooxmlsdk rig (github.com/arthrod/ooxmlsdk). This blocks the refinery's review/merge step and is causing read-only audit beads to fail at the review gate (deliverables sometimes still post, but the bead ends in 'failed').

Root cause (from check-run output): conclusion=failure, output.title="Kilo Code Review failed", output.summary="Review failed: Could not connect to the sandbox". 5m38s runtime, then failure.

PRs affected (recurring, not transient):

Pattern: intermittent but recurring across distinct PRs and over many hours. Other checks on the same commits (CodeRabbit, GitGuardian, Socket) pass, so it is specific to the Kilo Code Review sandbox, not the repo/CI runner.

Note: this is NOT a code defect in any PR — the redline code itself reviews fine. It is a Kilo Code Review sandbox-connectivity infrastructure failure that I cannot resolve from the town/mayor layer. Requesting investigation of the sandbox provisioning/connectivity for the code-review service.

Area

Merge Queue / Refinery

Context

  • Town ID: ab656b7a-8104-4ca8-b68e-1c2cb3df3d23
  • Agent: Mayor (b62d68f1-0594-4315-a29e-9803be13edfa)
  • Rig ID: 98f8cc04-56cb-4c5d-8d8a-4bb23c477156

Recent Errors

check-run Kilo Code Review: conclusion=failure, output.summary="Review failed: Could not connect to the sandbox" (PR #7, 2026-06-29T05:35:02Z; PR #10 same). Recurring same-class escalations on PR #17 (x2) and PR #18.

Filed automatically by the Mayor via gt_report_bug.

Activity

  1. jrf0110 commented on Aug 5, 2026

    @jrf0110
    Contributor

    Thanks for taking the time to report this and for helping us improve Gastown. We're sunsetting Gastown and winding down further product development, so we won't be taking this work on. We're closing this issue to keep the backlog accurate. We appreciate the detail and effort that went into the report.

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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions