Bug 835075

Summary:	Handle nonexistent sync history in repo summary table
Product:	[Community] PulpDist	Reporter:	Nick Coghlan <ncoghlan>
Component:	Web App	Assignee:	Nick Coghlan <ncoghlan>
Status:	CLOSED NEXTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	unspecified	Keywords:	Reopened
Target Milestone:	0.1.0
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	841498 (view as bug list)		Environment:
Last Closed:	2012-09-07 07:08:22 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	841498

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