Page MenuHomePhabricator

Fix an issue where non-ID changeset state keys were used as changeset IDs
ClosedPublic

Authored by epriestley on May 4 2020, 11:02 PM.
Tags
None
Referenced Files
F19096353: D21223.id.diff
Thu, Dec 4, 9:39 AM
F19083327: D21223.id50546.diff
Tue, Dec 2, 12:34 PM
F19080883: D21223.diff
Tue, Dec 2, 3:18 AM
F19080875: D21223.diff
Tue, Dec 2, 3:16 AM
F19080823: D21223.diff
Tue, Dec 2, 2:33 AM
F18985484: D21223.id50545.diff
Nov 17 2025, 1:04 PM
F18843491: D21223.diff
Oct 28 2025, 10:39 PM
F18827105: D21223.diff
Oct 24 2025, 7:46 AM
Subscribers
None

Details

Summary

Ref T13519. This is a little fuzzy, but I think the workflow here is:

  • View an intradiff, generating an ephemeral comparison changeset with no changeset ID. This produces a state key of "*".
  • Apply "hidden" state changes to the changeset.
  • View some other intradiff and/or diff view.
  • The code attempts to use "*" as a changset ID?

I'm not entirely sure this is accurate; this was observed in production and I couldn't get a clean reproduction case locally.

Optimistically, try making changeset IDs explicit rather than relying on state keys to be "usually changeset-ID-like".

Test Plan

Used "hidden" locally across multiple intradiffs, but I wasn't cleanly able to reproduce the initial issue.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable