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-611 yangtools <p>In some cases at least, when the yangtools yang parser fails, it does not say WHERE (while processing WHICH *.yang file) it fell over. Strangely, I have seen a case (see below) where it gives a line / column information, but not which model file.</p> <p>I'll see if I can contribute a change to address this.</p> <p><span class="error">&#91;main&#93;</span> ERROR org.opendaylight.yangtools.yang2sources.plugin.YangToSourcesProcessor - yang-to-sources: Unable to parse yang files from /home/vorburger/dev/ODL/git/controller/opendaylight/md-sal/samples/toaster-consumer/src/main/yang<br/> java.lang.IllegalArgumentException: config:disable-osgi-service-registration is not a YANG statement or use of extension. Source: null:19:9<br/> at com.google.common.base.Preconditions.checkArgument(Preconditions.java:145)<br/> at org.opendaylight.yangtools.yang.parser.impl.YangStatementParserListenerImpl.enterStatement(YangStatementParserListenerImpl.java:88)<br/> at org.opendaylight.yangtools.antlrv4.code.gen.YangStatementParser$StatementContext.enterRule(YangStatementParser.java:113)<br/> at org.antlr.v4.runtime.tree.ParseTreeWalker.enterRule(ParseTreeWalker.java:66)<br/> at org.antlr.v4.runtime.tree.ParseTreeWalker.walk(ParseTreeWalker.java:49)<br/> at org.antlr.v4.runtime.tree.ParseTreeWalker.walk(ParseTreeWalker.java:52)<br/> at org.antlr.v4.runtime.tree.ParseTreeWalker.walk(ParseTreeWalker.java:52)<br/> at org.opendaylight.yangtools.yang.parser.stmt.rfc6020.YangStatementSourceImpl.writeFull(YangStatementSourceImpl.java:94)<br/> at org.opendaylight.yangtools.yang.parser.stmt.reactor.SourceSpecificContext.loadStatements(SourceSpecificContext.java:320)<br/> at org.opendaylight.yangtools.yang.parser.stmt.reactor.BuildGlobalContext.loadPhaseStatements(BuildGlobalContext.java:206)<br/> at org.opendaylight.yangtools.yang.parser.stmt.reactor.BuildGlobalContext.buildEffective(BuildGlobalContext.java:174)<br/> at org.opendaylight.yangtools.yang.parser.stmt.reactor.CrossSourceStatementReactor$BuildAction.buildEffective(CrossSourceStatementReactor.java:105)<br/> at org.opendaylight.yangtools.yang.parser.stmt.reactor.CrossSourceStatementReactor$BuildAction.buildEffective(CrossSourceStatementReactor.java:123)<br/> at org.opendaylight.yangtools.yang2sources.plugin.YangToSourcesProcessor.processYang(YangToSourcesProcessor.java:169)<br/> at org.opendaylight.yangtools.yang2sources.plugin.YangToSourcesProcessor.execute(YangToSourcesProcessor.java:93)<br/> at org.opendaylight.yangtools.yang2sources.plugin.YangToSourcesMojo.execute(YangToSourcesMojo.java:116)</p> <p>Operating System: All<br/> Platform: All</p> YANGTOOLS-611

YANG Parser (sometimes) has Source: null, making it hard to track which source model file an error is in

Bug Verified Done Unassigned Michael Vorburger Thu, 12 May 2016 11:01:32 +0000 Sun, 10 Apr 2022 18:35:47 +0000 Mon, 20 Nov 2017 13:20:05 +0000 2.0.0 0 2 <p>Well, a file name is not necessarily available, as it can be something loaded in memory or similar. Getting line/column is something that can be done from any data stream.</p> <p>I think in this particular case the model is being resolved from a dependency jar &#8211; but steps to reproduce would be helpful.</p> <p>Hi Michael, are you currently working on this bug ? If so, could you please set the status to IN_PROGRESS and also the target milestone. Otherwise put it back into the queue. Thx</p> <p>This boils down to migrating downstreams to use yang-test-util with appropriate methods, such that the stream identity is not lost. For that we may need a couple of new methods.</p> <p>Fixed with elimination of <a href="https://git.opendaylight.org/gerrit/62537" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/62537</a>, which forces proper identity to be retained. Also previous work has migrated IllegalArgumentExceptions to SourceExceptions, which retain this information.</p> Development External issue ID 5881 External issue URL Issue Type Rank 0|i028an: