11

Steps to reproduce:

  1. Find a post that has been edited at least once.

  2. Go to the revisions history

  3. Click 'Edit' on an earlier revision:

  4. Do not edit the body, just add a random edit summary.

  5. Submit your edits.

Now you're one of the post editors, however, your name doesn't show in its revision history nor is the edit registered under "posts edited" in your profile! The problem is, I haven't managed to reproduce the bug in some posts, while in others, I have.

What's going on?

Improve this question
5
  • 1
    I think this should be fixed, given that this is the officially documented way to specify a reason for a rollback.
    – Sonic the Anonymous Hedgehog
    Commented Sep 15, 2021 at 20:18
  • 2
    That other post was mistagged, I forgot to update the tags. Fix had been deployed since 2021-09-15 15:31Z, approximately three hours ago. It's unclear to me that the fix deployed three hours ago would have caused this issue - this may have been another problem caused by the original change that caused the bug yesterday?
    – Kyle Pollard StaffMod
    Commented Sep 15, 2021 at 20:19
  • 1
    @double-beep Just to confirm - were all four of the posts you referenced done using the reproduction steps in your post, or is there a chance some were done with the Rollback button?
    – Kyle Pollard StaffMod
    Commented Sep 15, 2021 at 20:28
  • 2
    @KylePollard I reproduced this on a CW answer, but I did the "common edit flow": 1. Find the answer; 2. Click edit; 3. Click "Save edits" (without changing anything, nor adding a summary). The question in home page shows that I modified something
    – Rafael Tavares
    Commented Sep 15, 2021 at 20:51
  • 1
    @KylePollard nope, 2 other users (including me) participated in the experiment. Consistently reproduceable - steps taken have been identical. As a tangential observation, those edits do not show up in the API so it appears as if they are never submitted in the first place
    – 0Valt
    Commented Sep 15, 2021 at 21:32

1 Answer 1

Reset to default
11

This bug was indeed related to the bug that we fixed yesterday - it's not that our bug broke other things, but that our fix didn't catch everything affected. We're getting a fix out tonight. Thank you so much for reporting. We did a quick check and it looks like rollbacks on approximately 64 posts across all of Stack Exchange were affected over the past couple of days.

Improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .