Today, in our current setup, it happened that an accepted diff was closed by a commit. However, at the same time, another developer accepted the diff.
Presumable because of a race condition in the flow of actions, this caused the diff to be re-opened in an accepted state.
Attached a screenshot of the header and timeline of the diff in the final state.
{F1186210}
**Reproduction steps**
We didn't manage to //reproduce//, only to //produce//, see the attached screenshot. This on its own is enough to identify that the bug exists, but since this is probably the cause of a race condition, reproducing is not very deterministic.
**Version information**
| **phabricator** | 22bf88a2c91776d2854bd83f7a4cf7ebca0eba09 (Tue, Mar 22) |
| **arcanist** | 3d7ac867f53892b8210339bbb0c5fd91e0e36d78 (Tue, Mar 15) |
| **phutil** | b4f38af384807b7dcd1e3d1a96e9e9069e4d6964 (Fri, Mar 18) |