I think there is a small bug. Please look at the picture below. Since bounty period ended 23 hours ago, its grace period should not be ended yet. But it says it did.

enter image description here

  • 8
    Why would you not only not link to the question, but blank out completely public information? Jan 5 '12 at 21:43
  • 1
    It still shows on the "active" sub-tab of his Bounties tab. Interesting.
    – user154510
    Jan 5 '12 at 21:47
  • @MatthewRead Well, it must still be active if the box is showing up on the post. It looks like it should end at 21:50Z Jan 5 '12 at 21:48
  • 1
    @MichaelMrozek Sorry, it was dumb. Hiding identity must've become my habit. Jan 5 '12 at 21:52
  • I assume the "auto awarding" is done via a job, e.g. running every hour over all ended bounties granting to highest voted answer etc. So I would wait until 22:50Z (40 minutes from now) before starting to worry. Jan 5 '12 at 22:11
  • Hmm.. still nothing. Guess it's a bug then! Jan 5 '12 at 23:03

In my opinion, this is a bug, and it has nothing to do with when the hourly job runs.

bounty was added at 16:25

grace period expired at 15:25

As you can see, the bounty was added at 16:25, but the grace period expired at 15:25.

I haven't been awarded the bounty yet and I don't know when it will happen, but the grace period either hasn't ended yet or it was only 23 hours long.

  • If feel you're right, and not meaning to be nit picking: why do you say the grace period ended 15:25? To be super precise, shouldn't that read: it ended somewhere before 15:38? Or do you have some other info too? (As an aside: you can also hover the "23 hours" to see the bounty times.)
    – Arjan
    Jun 23 '12 at 16:05
  • Ah, Won't's profile still lists it as being in the grace period.
    – Arjan
    Jun 23 '12 at 16:10
  • 1
    I have checked the page at 15:27 or something, so I'm pretty sure the grace period timer just has a rounding bug.
    – Dennis
    Jun 23 '12 at 16:14
  • Bounty got auto-awarded at 17:35.
    – Dennis
    Jun 23 '12 at 17:36
  • I guess we'll never know if Won't could actually still award it manually during the last hour. I've one expiring in three days; maybe I am around to test then... The bug shouldn't be too hard to find though, I guess.
    – Arjan
    Jun 23 '12 at 17:39
  • 2
    There was another bug here with display only (not the awarding) which used .TotalHours on a TimeSpan that messed up the display on the last hour...it's been re-written for the next build and will now display correctly. Jun 23 '12 at 18:41

The bounty auto-award job does indeed run once an hour, there may be a gap between when the bounty ends and when that runs that you'll see an oddity like this, it's normal.

  • 1
    There was that, but the bug he actually reported is that the grace period ended less that 24 hours after the bounty did. That seems wrong and unrelated to the hourly job Jan 6 '12 at 15:45
  • 2
    I don't think this is by design. I took a few screenshots to support my claim. Please take a look at my answer.
    – Dennis
    Jun 23 '12 at 15:46

You must log in to answer this question.

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