oops when using last-updated

Bug #1397719 reported by Michael Nelson on 2014-11-30
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Click Package Index
Low
Unassigned

Bug Description

There are four oopses for 2014-11-29 [1], all related to last-updated, which seem to be parsing errors of the date:

 * IllegalArgumentException[Invalid format: "2014-" is malformed at "-"
 * IllegalFieldValueException[Cannot parse "2014-0": Value 0 for monthOfYear must be in the range [1,12]

[1] https://oops.canonical.com/static-reports/Click-Index-Prod-2014-11-29.html

See also traceback at https://pastebin.canonical.com/124240/

James Tait (jamestait) wrote :

This was me. :)

I was trying to see if I could craft a query along the lines of "show me all packages updated today". Unfortunately, the phone issues a new request for each character typed into the search bar, so while I was constructing my query string ("?q=last_updated:2014-01-01" to try and get anything updated this year), incomplete queries were being issued.

James Tait (jamestait) on 2014-12-04
Changed in click-package-index:
status: New → Confirmed
importance: Undecided → Low
James Tait (jamestait) on 2015-03-25
description: updated
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers