670653 - [traceback] Some tweets can cause ValueErrors

Status: RESOLVED INCOMPLETE

(support.mozilla.org :: Army of Awesome, task)

Description

[James Socol [:jsocol, :james]]

I'm not sure exactly what happens here, but it looks like some tweets are coming in with bad data and can't be rendered back out. Here's the stack trace:

Traceback (most recent call last):

  File "/data/www/support.mozilla.com/kitsune/vendor/src/django/django/core/handlers/base.py", line 111, in get_response
    response = callback(request, *callback_args, **callback_kwargs)

  File "/data/www/support.mozilla.com/kitsune/vendor/src/django/django/views/decorators/http.py", line 45, in inner
    return func(request, *args, **kwargs)

  File "/data/www/support.mozilla.com/kitsune/apps/customercare/views.py", line 102, in more_tweets
    filter=filter)})

  File "/data/www/support.mozilla.com/kitsune/apps/customercare/views.py", line 88, in _get_tweets
    return [_tweet_for_template(tweet) for tweet in q]

  File "/data/www/support.mozilla.com/kitsune/apps/customercare/views.py", line 39, in _tweet_for_template
    date = datetime(*parsed_date[0:6])

ValueError: hour must be in 0..23


As far as I can tell, these are caused by a few specific tweets. zh-CN has one at the moment.

Comment 1

[Ricky Rosario [:rrosario, :r1cky]]

Cleaning up 2011Q4

Comment 2

[Will Kahn-Greene [:willkg] ET needinfo? me]

I haven't seen anything about this in years. Going to close it out. If it's still an issue, we can re-open it.