6

In this answer, Sklivvz announced that in the next built after the 21st, 13:37 UTC, the Snaphat should be fixed and working as described.

Yet I was awarded the Snaphat twice without the conditions being met:

  • This answer:

    • 23rd,   9:15: question posted
    • 23rd, 10:52: answer posted (97 minutes later)
    • 23rd, 15:42: other criteria fulfilled¹
  • This answer:

    • 23rd, 18:30: question asked
    • 24th, 10:37: answer posted (16 hours later)
    • 24th, 23:54: other criteria fulfilled¹

I do not know, how often builts are dispatched, but IIRC it was considerably less than three days. Therefore I assume that something is still not fixed.

¹ I know that this time is not supposed to count towards the thirty minutes in the description. However, this is when the hat could first be awarded and thus the crucial time at which the hat-awarding routine was still faulty.

  • FYI You can see the build number (which includes the deployment date) at the bottom left of every page – Cai Dec 25 '16 at 8:52
  • Hmm, that’s the 24th, which might still fit into this by six minutes. Now the question is whether there was any built in between. – Wrzlprmft Dec 25 '16 at 9:04
  • I got it on this just now, when I posted the answer after 30 minutes. – Mithical Dec 25 '16 at 15:58
  • Still not fixed. I got Snaphat just now on SA. My answer came over two hours after the question was asked. cooking.stackexchange.com/questions/77037/… As a note, I also was not first to answer... All I did was answer, get three upvotes and be accepted. – Catija Jan 2 '17 at 22:15
  • 1
    Try this one for size: I got Snaphat by editing an old answer (not posted within 30 minutes of the question) that subsequently got an upvote, pushing it to 3. – Jeroen Mostert Jan 3 '17 at 10:24
  • I'm looking to see what's going on with this. – Taryn Jan 3 '17 at 15:21
3

Yes, you are correct the hat was still being awarded wrong. There was a bug that we missed in the query that has now been fixed. Can you spot the bug in the line of code causing the problem?

And DateDiff(minute, a.CreationDate, q.CreationDate) <= 30

Basically, we had the answer creation date in the wrong position for the date comparison. Being in the wrong position it always resulted in a negative number. The negative value meant that the hat was being awarded outside of the 30 minutes was supposed to be required. The bug has since been squashed and the hat should now be awarded properly.

  • Just curious, are all the checks performed in the database level? – Shadow The Princess Wizard Jan 4 '17 at 13:29
  • 1
    Also... are you a dev or CM? ;-) – Shadow The Princess Wizard Jan 4 '17 at 13:29
  • @ShadowWizard the SQL is inline in the codebase. Not a dev just someone who pokes around the code and knows sql. – Taryn Jan 4 '17 at 13:51
  • 3
    So, you're kind of... Code Manager? :D – Shadow The Princess Wizard Jan 4 '17 at 13:52
  • Shhhh @ShadowWizard don't give away all my secrets – Taryn Jan 4 '17 at 13:54

You must log in to answer this question.

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