Bug 33750
| Summary: | Overview entries without "priority" are placed first | ||
|---|---|---|---|
| Product: | UCS | Reporter: | Alexander Kläser <klaeser> |
| Component: | Apache | Assignee: | Lukas Walter <walter> |
| Status: | CLOSED FIXED | QA Contact: | Alexander Kläser <klaeser> |
| Severity: | minor | ||
| Priority: | P5 | CC: | gohmann, jmm |
| Version: | UCS 3.2 | ||
| Target Milestone: | UCS 3.2-2-errata | ||
| Hardware: | Other | ||
| OS: | Linux | ||
| 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: | Flags outvoted (downgraded) after PO Review: | ||
| Ticket number: | Bug group (optional): | Cleanup | |
| Max CVSS v3 score: | |||
| Attachments: | Patch | ||
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 (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) |
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).