Bug 835075 - Handle nonexistent sync history in repo summary table
Summary: Handle nonexistent sync history in repo summary table
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: PulpDist
Classification: Community
Component: Web App
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: 0.1.0
Assignee: Nick Coghlan
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 841498
TreeView+ depends on / blocked
 
Reported: 2012-06-25 13:17 UTC by Nick Coghlan
Modified: 2012-09-07 07:08 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 841498 (view as bug list)
Environment:
Last Closed: 2012-09-07 07:08:22 UTC
Embargoed:

Attachments (Terms of Use)

Description Nick Coghlan 2012-06-25 13:17:27 UTC 
Description of problem:

The repo summary table may error out if sorting the columns without any sync history.

Solution is to calculate appropriate values for all columns in RepoListView, rather than attempting to access index 0 of the sync history in RepoTable columnn definitions.

See https://github.com/bradleyayers/django-tables2/issues/81
Comment 1 Nick Coghlan 2012-07-12 06:11:45 UTC 
Updated for 0.0.18
Comment 2 Nick Coghlan 2012-07-25 05:08:52 UTC 
Expected behaviour: repo summary table can be sorted correctly (this bug was really easy to trigger once BZ#839139 was fixed, as the site metadata "repo" never has a sync history)
Comment 3 Nick Coghlan 2012-09-07 07:08:22 UTC 
Fixed in 0.1.0
Note You need to log in before you can comment on or make changes to this bug.