Bug 33750 - Overview entries without "priority" are placed first
Overview entries without "priority" are placed first
Status: CLOSED FIXED
Product: UCS
Classification: Unclassified
Component: Apache
UCS 3.2
Other Linux
: P5 minor (vote)
: UCS 3.2-2-errata
Assigned To: Lukas Walter
Alexander Kläser
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-12-13 13:00 CET by Alexander Kläser
Modified: 2014-07-02 11:28 CEST (History)
2 users (show)

See Also:
What kind of report is it?: ---
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Ticket number:
Bug group (optional): Cleanup
Max CVSS v3 score:


Attachments
Patch (566 bytes, patch)
2013-12-13 13:00 CET, Alexander Kläser
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Kläser univentionstaff 2013-12-13 13:00:36 CET
Created attachment 5699 [details]
Patch

… ideally they should be placed at the end of the list. The attached patch fixes this. The order is computed lexicographically, as fallback value for priority, float("inf") (i.e., a number) is used. The patch replaces this with "~" (which has the highest order for ascii characters).
Comment 1 Lukas Walter univentionstaff 2014-06-18 16:01:39 CEST
Patch didn't do the trick as "priorty" was not actually missing in the related dict, but set to empty string not triggering the return of a default value. 

Instead of applying the patch, I've modified the initial value for the priority: 
empty string -> "~"


svn 51177: univention-apache (6.0.16-7)
svn 51178: YAML
Comment 2 Alexander Kläser univentionstaff 2014-06-19 12:32:10 CEST
(In reply to Lukas Walter from comment #1)
> Patch didn't do the trick as "priorty" was not actually missing in the
> related dict, but set to empty string not triggering the return of a default
> value. 
> 
> Instead of applying the patch, I've modified the initial value for the
> priority: 
> empty string -> "~"

Patch works fine for me. The priority is now explicitely set to "~" in the json file, but this is ok.

YAML file → OK (with minor adjustment + line break fix)
Comment 3 Moritz Muehlenhoff univentionstaff 2014-07-02 11:28:34 CEST
http://errata.univention.de/ucs/3.2/131.html