For example on meta I have a bounty that expires in 2 hours: 2 hours

Ok so fine. I have 2 more hours until the bounty on this question expires and noone else can post an answer that is eligible.

On stack I have a question on which the bounty expired and I have yet to select an answer and that looks like this:

24 hours? From when?

24 Hours? From when? Yesterday. Wow that is very descriptive...

Can we please make it so that the time for selecting an answer after a bounty has expired is just as dynamic as before it expired?


This is what it says when I hover over the word yesterday:

started at 2011-11-30 15:10:45Z
ended at 2011-12-07 15:10:45Z

  • 1
    Did you try hovering over "yesterday"? – Pekka Dec 8 '11 at 15:51
  • Are you sure the message won't update in an hour to say "23 hours"? I think it does, but I won't swear to it on the spot. – Adam Lear Dec 8 '11 at 15:52
  • Anna's right. You did actually have 24 hours from the moment you took the screenshot, rounded to the nearest hour. – Pops Dec 8 '11 at 15:54
  • @AnnaLear it has said 24 Hours since yesterday. I am updating my question with the hover over the word yesterday – Naftali aka Neal Dec 8 '11 at 15:54
  • @PopularDemand see my above comment. and I had just taken that screenshot before posting – Naftali aka Neal Dec 8 '11 at 15:54
  • @Pekka yes. see update. But that doesnt change the fact that the bold words should be updated in the same way. – Naftali aka Neal Dec 8 '11 at 15:56
  • Whoops, I thought today was the 7th. I guess I once saw a bounty with a small amount of time left (like in your first screenshot) and misremembered it. – Pops Dec 8 '11 at 15:57
  • @PopularDemand lol nope :-P – Naftali aka Neal Dec 8 '11 at 15:57
  • This "This question had a bounty worth +50 reputation from Neal that ended yesterday; grace period ends in 24 hours" used to read something like "This question had a bounty worth +50 reputation from ... that ended xx hours ago." Still seems to me that the system thinks there's actually 24 hours left. (Though I know that does not match the time stamps you're seeing.) – Arjan Dec 8 '11 at 16:07
  • Hmm, maybe my memory of dynamic/changing numbers during the grace period wasn't crazy after all. Perhaps when they changed the message format, they introduced a bug in the time math? Good find, @Arjan. – Pops Dec 8 '11 at 16:09
  • @Arjan lol I have no idea – Naftali aka Neal Dec 8 '11 at 16:10

Oops, nice find, thanks.

This was the classic bug of DateTime.Hours (here) versus DateTime.TotalHours (here).

Fixed in the next build.

  • Haha. Thank you. Odd. It now says I have 23 Hours to award the bounty. Why is that? – Naftali aka Neal Dec 8 '11 at 16:16
  • 1
    @amanaPlanaCAnalPAnaMA: Because the scheduled job that closes expired bounties hasn't run yet. You should hurry up if you want to award it. – balpha Dec 8 '11 at 16:18
  • Don't I have 24 hours since it expired. Do you know how long I have left? – Naftali aka Neal Dec 8 '11 at 16:19
  • 2
    You don't have any time left. As soon as the scheduled job runs (it happens hourly), the bounty is gone. So, anywhere between zero and fifty minutes. – balpha Dec 8 '11 at 16:20
  • Wow. ok ^_^ I am fine with losing the bounty. I need to set up a new one, I did not get anything good. – Naftali aka Neal Dec 8 '11 at 16:21

You must log in to answer this question.

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