https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/YANGTOOLS-505 yangtools <p>I (mis)defined a union as this (missing 'type' keywords inside the union):</p> <p> leaf datapath-id {<br/> type union </p> { yang-types:hex-string; uint64; } <p>The parser did not complain, but at run time i got the following exception:</p> <p>2015-09-14 19:41:54,787 | WARN | bundle-tracker-0 | YangParserImpl | 79 - org.opendaylight.yangtools.yang-parser-impl - 0.8.0.SNAPSHOT | Error in module of-l3-topology at line 89: Failed to resolve node urn:ietf:params:xml:ns:yang:ietf-yang-types:hex-string : no such extension definition found.<br/> 2015-09-14 19:41:54,787 | WARN | bundle-tracker-0 | YangParserImpl | 79 - org.opendaylight.yangtools.yang-parser-impl - 0.8.0.SNAPSHOT | Error in module of-l3-topology at line 90: Failed to resolve node urn:opendaylight:openflow-pce-topology:uint64 : no such extension definition found.<br/> 2015-09-14 19:41:55,054 | WARN | bundle-tracker-0 | YangParserImpl | 79 - org.opendaylight.yangtools.yang-parser-impl - 0.8.0.SNAPSHOT | Error in module of-l3-topology at line 89: Failed to resolve node urn:ietf:params:xml:ns:yang:ietf-yang-types:hex-string : no such extension definition found.<br/> 2015-09-14 19:41:55,054 | WARN | bundle-tracker-0 | YangParserImpl | 79 - org.opendaylight.yangtools.yang-parser-impl - 0.8.0.SNAPSHOT | Error in module of-l3-topology at line 90: Failed to resolve node urn:opendaylight:openflow-pce-topology:uint64 : no such extension definition found.<br/> 2015-09-14 19:41:55,386 | WARN | bundle-tracker-0 | YangParserImpl | 79 - org.opendaylight.yangtools.yang-parser-impl - 0.8.0.SNAPSHOT | Error in module of-l3-topology at line 89: Failed to resolve node urn:ietf:params:xml:ns:yang:ietf-yang-types:hex-string : no such extension definition found.<br/> 2015-09-14 19:41:55,386 | WARN | bundle-tracker-0 | YangParserImpl | 79 - org.opendaylight.yangtools.yang-parser-impl - 0.8.0.SNAPSHOT | Error in module of-l3-topology at line 90: Failed to resolve node urn:opendaylight:openflow-pce-topology:uint64 : no such extension definition found.<br/> 2015-09-14 19:41:55,878 | WARN | ty-notifications | YangParserImpl | 79 - org.opendaylight.yangtools.yang-parser-impl - 0.8.0.SNAPSHOT | Error in module of-l3-topology at line 89: Failed to resolve node urn:ietf:params:xml:ns:yang:ietf-yang-types:hex-string : no such extension definition found.<br/> 2015-09-14 19:41:55,878 | WARN | ty-notifications | YangParserImpl | 79 - org.opendaylight.yangtools.yang-parser-impl - 0.8.0.SNAPSHOT | Error in module of-l3-topology at line 90: Failed to resolve node urn:opendaylight:openflow-pce-topology:uint64 : no such extension definition found.</p> <p>The parser should catch this syntax error.</p> <p>Operating System: All<br/> Platform: All</p> YANGTOOLS-505

malformed union type not caught at compile time

Bug Resolved Done Unassigned Jan Medved Tue, 15 Sep 2015 02:48:48 +0000 Sun, 10 Apr 2022 18:35:37 +0000 Fri, 18 Dec 2015 09:03:31 +0000 0 4 <p>Hi Jan</p> <p>Basically, both (mis)defined statements were recognized as unknown ones. <br/> Obviously, there are no such extensions defined, so warning messages are valid.</p> <p>If we want parser to recognize this type of input error, we would need to implement extra functionality to check all TYPE statements afterwards and inform user accordingly.</p> <p>The parser should be reacting rather strongly to such a yang file now &#8211; is this still reproducible (e.g. silent failure)?</p> <p>It is a silent failure in the sense that it gets detected at run time, not at compile time. Compilation finished just fine.</p> <p>This issue is resolved in current yangtools code base, please retry</p> <p>latest related patch: <a href="https://git.opendaylight.org/gerrit/#/c/30202/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/30202/</a></p> Blocks YANGTOOLS-550 Development External issue ID 4310 External issue URL Issue Type ODL SR Target Milestone Rank 0|i027n3: