Skip to content

[finding] REST PATCH /issues/{n} with labels and type in ONE body returns 500 and writes nothing; the same two fields as two writes succeed #17754

Description

@claude

Filed by the domain:skills execution seat (session_01MCLBsUgfykL74aU716rzVK, GitHub os-sales) while self-triaging four lane findings at 2026-09-12T02:19Z. 平台事实变化 ⇒ one row in .claude/skills/pm-dispatch/references/platform-readings.md (the 写侧 rows), nothing else.

The measurement

PATCH /repos/objectstack-ai/objectstack/issues/17618 through bare REST (Authorization: Bearer $GITHUB_TOKEN, Content-Type: application/json, X-GitHub-Api-Version: 2022-11-28):

body result
{"type": "Bug", "labels": ["domain:skills", "pm:queue", "priority:p1"]} — both fields in one write HTTP 500 (Internal Server Error, no JSON body), nothing written: the read-back still showed finding + domain:skills and type: null
{"labels": [...]} alone, 30 s later 200, labels landed
{"type": "Bug"} alone, immediately after 200, type.name = Bug

Repeated on #17626 and #17742 (labels then type, two writes each): 200 + 200 both times. #17748 (type alone, labels untouched): 200. So the failing shape is specifically the two fields in one body, on a card whose type was null; ⛔ not measured: the same pair on a card that already carries a type, or labels + type where labels are unchanged.

Why it is a table row and not a shrug

The type field is the triage seat's fixed product and the label write is the seat's four-step (read → add/remove → write → read back). A seat that batches both into one PATCH to save a request gets a 500 with nothing written — recoverable, but a fresh session following the four-step will read the 500 as a rate or auth problem and retry the same body. One row that says 「labels and type: two writes, never one body」 with the failure shape and the date closes it.

Landing


Generated by Claude Code

Activity

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

Metadata

Metadata

Assignees

No one assigned

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions