Univention Bugzilla – Full Text Bug Listing |
Summary: | configRegistry[key] does not raise KeyError | ||
---|---|---|---|
Product: | UCS | Reporter: | Philipp Hahn <hahn> |
Component: | UCR | Assignee: | UCS maintainers <ucs-maintainers> |
Status: | REOPENED --- | QA Contact: | |
Severity: | enhancement | ||
Priority: | P5 | CC: | best, gohmann, wiesenthal |
Version: | UCS 5.0 | ||
Target Milestone: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
What kind of report is it?: | Development Internal | 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): | API change, Further conceptual development | |
Max CVSS v3 score: |
Description
Philipp Hahn
2012-08-22 13:27:43 CEST
Within univention.config_registry.interfaces VengefulConfigRegistry is used to wrap the ConfigRegistry instance to throw KeyErrors instead of returning '' for unset keys. This fixes the error of ipv6_gateway() always returning an error even is the value is unset. svn34995, univention-config-registry_8.0.2-4.394.201208221410 But the decision to change the default behaviour to generally throw a KeyError remains. (In reply to comment #1) > But the decision to change the default behaviour to generally throw a KeyError > remains. Yes, it makes sense. It is an API change, so UCS 4 would be the next version for this issue. (In reply to Stefan Gohmann from comment #2) > (In reply to comment #1) > > But the decision to change the default behaviour to generally throw a KeyError > > remains. > > Yes, it makes sense. It is an API change, so UCS 4 would be the next version > for this issue. In general it would be useful. But I think the benefit is less than the cost. It has to be changed in our and in all external code and we have to support both for a time. Removed UCS 4 target milestone. This issue has been filed against UCS 4.2. UCS 4.2 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed. If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you. |