Gwibber shows "BUG:00:00:59:63" instead of "<x> seconds ago" in Twitter timeline

Seen this too, confirming. Same version as bug reporter.

Probably a duplicate of bug #705674.

I see an inconsistency in the following code from util.py (condensed):

  elif d.seconds < 3600 and d.seconds >= 60:
    # ...
  elif round(d.seconds) < 60:
    # ...
  else: return "BUG: %s" % str(d)

Note the different handling of d.seconds: it is rounded in one expression but not the other. But I'm not fluent in Python so I don't know if this is significant or not.

I concocted a small test program that mimics the logic in util.py:
----
def testit(v):
    print(v)
    if v >= 60:
        print ">= 60"
    elif round(v) < 60:
        print "< 60"
    else: print "err"

testit(59.4)
testit(59.5)
testit(59.6)
testit(60)
----

Output:

59.4
< 60
59.5
err
59.6
err
60
>= 60

This seems to confirm my hypothesis.

This patch removes the rounding in the last elif condition, to avoid an error when the seconds part is between 59.5 and 60.0.

Ken, can you look at this patch please? :)

This bug was fixed in the package gwibber - 2.91.91.1-0ubuntu1

---------------
gwibber (2.91.91.1-0ubuntu1) natty; urgency=low

  * New upstream release
    - Remove the rounding in the last elif condition, to avoid an error when
      the seconds part is between 59.5 and 60.0. (Per Ångström) (LP: #705424)
    - Fixed handling of the in_reply_to data for twitter, and made minor
      changes to make sure identi.ca and status.net behaves the same
      way (LP: #677233)
 -- Ken VanDine <email address hidden> Fri, 11 Mar 2011 15:07:28 -0500