I just want to make sure.

My question was put on hold after having a status-completed tag.
Yes I know, chances are it is not really possible to reproduce but it was a known issue so I guess it is good that it was pointed out no ?

I mean... If the bug was fixed, off course it is not possible to reproduce it.

Was it off topic or not ?

  • It is kindof weird, fixed bugs aren't usually closed Dec 12, 2013 at 14:01
  • 2
    The explanation is in the close reason message: It can no longer be reproduced. So it was perfectly OK to ask, but also perfectly OK to close. I agree handling this under the "off-topic" heading is weird, though.
    – Pekka
    Dec 12, 2013 at 14:03
  • I think closing is appropriate when the issue can no longer be reproduced due to changes that weren't specifically meant to fix that issue. Perhaps tagging it as status-complete was incorrect in this case?
    – Stijn
    Dec 12, 2013 at 14:09
  • 3
    @Stijn so we need to remove the tag and close at least half the fixed bug reports here on Meta. After being fixed, 100% of the bugs can't be reproduced anyway otherwise it means they were not fixed. Dec 12, 2013 at 14:12
  • Probably people who voted to close could not reproduce it at no point in time - common problem with caching issues.
    – Mołot
    Dec 12, 2013 at 14:13
  • @Mołot Probably but still this shouldn't show up in the Off-Topic section. Dec 12, 2013 at 14:13
  • @ShaWizDowArd Should that close reason exist at all then?
    – Stijn
    Dec 12, 2013 at 14:14
  • Well, "cannot be reproduced" is offtopic on meta, and I think it was discussed already if it's right or wrong. But that's the way it is.
    – Mołot
    Dec 12, 2013 at 14:15
  • @Stijn of course, e.g. old bugs about things that does not exist anymore (envelope, faq pages, old top bar and more) Dec 12, 2013 at 14:15
  • 1
    @Mołot "I tried to access stack overflow and a cat jumped out of my computer" would reasonably be off topic--> It can no longer be reproduced. That sort of thing is off topic. But things that were fixed after the bug report seem on topic Dec 12, 2013 at 14:20
  • @RichardTingle But my guess was that first votes was cast before it was fixed. Cache glitches often can't be easily reproduced even before they are fixed.
    – Mołot
    Dec 12, 2013 at 14:22
  • @Mołot The question was closed two hours after the answer arrived. But yes, I imagine the first votes arrived before that. Dec 12, 2013 at 14:49
  • @Duncan well this post has my upvote and I think people should no longer vote to close when it was confirmed (and solved). Unless in reality it was fixed before it was even posted.
    – Mołot
    Dec 12, 2013 at 14:59
  • In addition to the previous comments, it's closed as "off topic" because meta has a custom close reason for "cannot be reproduced", and custom close reasons are designed so that they're all in the off topic category. Dec 12, 2013 at 16:14
  • @ʞunɥdɐpɐɥd I'm responding to this: "Probably but still this shouldn't show up in the Off-Topic section." As already mentioned in the comments and made obvious by the custom reason, no repro items are close targets. Why would I bother covering the same ground again? Dec 12, 2013 at 16:17

1 Answer 1


Reading the question carefully, it seems you noticed the symptom of an issue that had been fixed earlier in the day. I guess only caching problems can behave like that.

Arguably, your question shouldn't have been tagged since nothing was altered. However, I suspect this is often done out of politeness by the relevant developer.

I would say the tagging is the error here. A forgiveable one, since it's clearly good-natured. But your problem could not be reproduced (not even by yourself after the initial observation) and a developer confirmed the issue was already fixed.

  • 1
    The answer states that there was indeed an issue that was fixed in a recent change. The use of [status-completed] is probably OK. Dec 12, 2013 at 15:20

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