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-1465 yangtools <p>Full log attached.</p> <p>Affected models:</p> <p><a href="https://raw.githubusercontent.com/YangModels/yang/main/standard/ietf/RFC/ietf-te-topology-state@2020-08-06.yang" class="external-link" target="_blank" rel="nofollow noopener">https://raw.githubusercontent.com/YangModels/yang/main/standard/ietf/RFC/ietf-te-topology-state@2020-08-06.yang</a></p> <p><a href="https://raw.githubusercontent.com/YangModels/yang/main/standard/ietf/RFC/ietf-te-topology@2020-08-06.yang" class="external-link" target="_blank" rel="nofollow noopener">https://raw.githubusercontent.com/YangModels/yang/main/standard/ietf/RFC/ietf-te-topology@2020-08-06.yang</a></p> YANGTOOLS-1465

Unexpected error processing source SourceIdentifier [ietf-network@2018-02-26]

Bug High Resolved Done Robert Varga Mario Doman pt Thu, 10 Nov 2022 10:45:01 +0000 Thu, 24 Nov 2022 17:22:01 +0000 Thu, 24 Nov 2022 17:22:01 +0000 8.0.0 9.0.0 10.0.0 9.0.2 8.0.8 10.0.1 8.0.9 9.0.4 parser 0 2 <p><b>12:15:25</b> **************************************** ERROR IN YANG FILE /home/jenkins/src/main/yang/standard/ietf/RFC/ietf-te-topology-state.yang ****************************************<b>12:15:25</b> 11:11:20.799 <span class="error">&#91;main&#93;</span> WARN org.opendaylight.yangtools.yang.parser.stmt.reactor.BuildGlobalContext - Unexpected error processing source SourceIdentifier <span class="error">&#91;ietf-network-topology-state@2018-02-26&#93;</span>. Please file an issue with this model attached.</p> <p>Okay, so the key factor here is that the leaf is guarded by if-feature and yang-model-validator is running with empty features.</p> <p>This means the leaf should not be built, so the original has flags -88 == 0b10101000 which in turn decodes to:<br/> HAVE_IGNORE_IF_FEATURE | HAVE_SUPPORTED_BY_FEATURES | ALL_INDEPENDENT.</p> <p>So far this seems to involve undeclared case statements, which do not seem to realize they are no supported. This needs a bit of thought, as here we have an inverted parent-&gt;child causality: the child needs to be supported for the parent to be supported.</p> <p>The reproducer is a bit involved:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>module foo {  namespace foo;  prefix foo;  feature foo;  container foo;  augment /foo {    container bar {      choice baz {        mandatory true;        leaf one {          type string;        }        leaf two {          if-feature foo;          type string;        }      }    }  } } </pre> </div></div> <p>The problem seems to be the combination of augment, choice, implicit case and if-feature'd leaf. ietf-ip.yang triggers this as well, hence high priority.</p> <p>Also, the error path occurs under container foo, hence I think the crux of the issue is InferredStatementContext not consulting original's either isSupportedByFeatures(), or more likely isSupportedToBuildEffective().</p> Development Rank 0|i043dz: