findChangeLog: don't crash if sort is unspecified #2774

Closed
opened 2015-05-06 16:42:26 +00:00 by wjt · 2 comments

This would crash:

api.findChangeLogs(keys=[])

because there's no 'name' key for changelog entries. Instead, default to
chronological order, newest first.

This would crash: api.findChangeLogs(keys=[]) because there's no 'name' key for changelog entries. Instead, default to chronological order, newest first.
j added the
backend
label 2015-05-06 16:42:26 +00:00
j added this to the 14.04 milestone 2015-05-06 16:42:26 +00:00
j self-assigned this 2015-05-06 16:42:26 +00:00
j added the
normal
defect
labels 2015-05-06 16:42:26 +00:00
Author

Attachment 0001-findChangeLog-don-t-crash-if-sort-is-unspecified.patch (995 bytes) added

**Attachment** 0001-findChangeLog-don-t-crash-if-sort-is-unspecified.patch (995 bytes) added
Owner

fixed in []changeset:pandora,4963

fixed in []changeset:pandora,4963
j added the
fixed
label 2015-05-06 17:01:42 +00:00
j closed this issue 2015-05-06 17:01:42 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: 0x2620/pandora#2774
No description provided.