If an attempt is made to view a release (i.e., release encoding) that has an associated file that has no associated track, things break
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Resonate |
Fix Committed
|
High
|
Unassigned |
Bug Description
Why should a release have a file with an unassociated track? Well, I don't think it should -- there is currently a bug in the collection-
Here's an example stack trace...
Traceback (most recent call last):
File "/home/
return render_
File "/home/
return HttpResponseOka
File "/home/
return _get_template_
File "/home/
{% extends "members/base.tpl" %}
File "/home/
{% extends "base.tpl" %}
File "/home/
{% extends "bare-base.tpl" %}
File "/home/
{% block body %}
File "/home/
{% block body_container %}
File "/home/
{% block content %}
File "/home/
{% for f in release.
File "/home/
return __obj(*args, **kwargs)
File "/home/
return sorted(files, cmp=tracknum_
File "/home/
def tracknum_
AttributeError: 'NoneType' object has no attribute 'track_num'
Changed in resonate: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Changed in resonate: | |
importance: | Medium → High |
summary: |
If an attempt is made to view a release (i.e., release encoding) that - has an associated file that has no associated track, thnigs break + has an associated file that has no associated track, things break |
description: | updated |
Fixed in revision 823.