<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 20:54:19 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>OpenDaylight JIRA</title>
    <link>https://jira.opendaylight.org</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>8.20.10</version>
        <build-number>820010</build-number>
        <build-date>22-06-2022</build-date>
    </build-info>


<item>
            <title>[YANGTOOLS-789] Errors on augments to nodes in groupings</title>
                <link>https://jira.opendaylight.org/browse/YANGTOOLS-789</link>
                <project id="10188" key="YANGTOOLS">yangtools</project>
                    <description>&lt;p&gt;On the parsing of the models of one of our devices, we are getting errors on augments not finding their targets.   This is always in combination with nested groupings, where the target is somewhere in the nested grouping.&lt;/p&gt;

&lt;p&gt;I&apos;ve attached a minimal model to this bug report.  It is the original model that failed (with some IETF and BBF models), but I&apos;ve removed everything that is not related to the problem, to have a minimal model to investigate with.  I couldn&apos;t see an issue with the models however.   &lt;/p&gt;

&lt;p&gt;Note also that in some occasions the parsing succeeds, and in others it fails.   I&apos;ve not been able to find the environment difference between the 2 systems that would influence this.&lt;/p&gt;

&lt;p&gt;I&apos;ve also attached a file with debug logging from the error.&lt;/p&gt;</description>
                <environment>&lt;p&gt;Operating System: All&lt;br/&gt;
Platform: All&lt;/p&gt;</environment>
        <key id="23209">YANGTOOLS-789</key>
            <summary>Errors on augments to nodes in groupings</summary>
                <type id="10104" iconUrl="https://jira.opendaylight.org/secure/viewavatar?size=xsmall&amp;avatarId=10303&amp;avatarType=issuetype">Bug</type>
                                                <status id="5" iconUrl="https://jira.opendaylight.org/images/icons/statuses/resolved.png" description="A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.">Resolved</status>
                    <statusCategory id="3" key="done" colorName="green"/>
                                    <resolution id="10003">Cannot Reproduce</resolution>
                                        <assignee username="pkajsa">Peter Kajsa</assignee>
                                    <reporter username="verthezpw">Peter Verthez</reporter>
                        <labels>
                    </labels>
                <created>Mon, 19 Jun 2017 07:48:13 +0000</created>
                <updated>Sun, 10 Apr 2022 18:36:00 +0000</updated>
                            <resolved>Mon, 17 Jul 2017 06:09:43 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>1</watches>
                                                                                                                <comments>
                            <comment id="44452" author="verthezpw" created="Mon, 19 Jun 2017 07:48:13 +0000"  >&lt;p&gt;Attachment augments.zip has been added with description: minimized model showing the bug&lt;/p&gt;</comment>
                            <comment id="44453" author="verthezpw" created="Mon, 19 Jun 2017 07:50:53 +0000"  >&lt;p&gt;Attachment error.txt.gz has been added with description: debug logging&lt;/p&gt;</comment>
                            <comment id="44446" author="pkajsa" created="Thu, 6 Jul 2017 08:38:10 +0000"  >&lt;p&gt;Hi,&lt;/p&gt;

&lt;p&gt;I have been trying to replicate this bug with the attached yang models, however without any success. I run the test in loop thousand times, but SchemaContext is always created successfully. Please are you sure, there is not something else what has influence on the bug occurrence (e.g. loading of an another revision of a module under some conditions etc.) or something what is missing in the attached set of yang models ?&lt;/p&gt;

&lt;p&gt;Thanks.&lt;/p&gt;</comment>
                            <comment id="44447" author="verthezpw" created="Thu, 6 Jul 2017 08:42:41 +0000"  >&lt;p&gt;We have several modules with independent models.&lt;/p&gt;

&lt;p&gt;However, for this parsing we are not using the SharedSchemaRepository, but&lt;/p&gt;

&lt;p&gt;CrossSourceStatementReactor.BuildAction reactor = YangInferencePipeline.RFC6020_REACTOR.newBuild(supportedFeatures);&lt;br/&gt;
reactor.addSources(moduleSources);&lt;br/&gt;
schemaContext = reactor.buildEffective();&lt;/p&gt;

&lt;p&gt;So I was assuming that there could be no interference between the modules.  Or is this not correct?   Can the parsing result depend on earlier parse results?   If so, how can we avoid that?&lt;/p&gt;</comment>
                            <comment id="44448" author="pkajsa" created="Fri, 7 Jul 2017 09:49:48 +0000"  >&lt;p&gt;The code you posted is also standard way how to use parser, so I think there should not be any interference between models. Parsing result should not depend on earlier parse results, otherwise there is a bug. &lt;/p&gt;

&lt;p&gt;I will try to perform further investigation. If you find some new info that could help to replicate the bug, please let me know. &lt;/p&gt;

&lt;p&gt;Thanks.&lt;/p&gt;</comment>
                            <comment id="44449" author="verthezpw" created="Mon, 10 Jul 2017 07:31:29 +0000"  >&lt;p&gt;OK, I will investigate further from my end as well.&lt;/p&gt;</comment>
                            <comment id="44450" author="verthezpw" created="Tue, 11 Jul 2017 10:30:27 +0000"  >&lt;p&gt;I and some other people have tried to investigate the issue, but apparently we can&apos;t reproduce it anymore either (although it was reproduced by multiple people before).   We don&apos;t exactly know why however.&lt;/p&gt;

&lt;p&gt;But in any case, I think you can close this issue and stop further investigating it.   If it reoccurs, we will investigate first on our side.&lt;/p&gt;</comment>
                            <comment id="44451" author="pkajsa" created="Mon, 17 Jul 2017 06:09:43 +0000"  >&lt;p&gt;Ok, thanks.&lt;/p&gt;</comment>
                    </comments>
                    <attachments>
                            <attachment id="13080" name="augments.zip" size="47524" author="verthezpw" created="Mon, 19 Jun 2017 07:48:13 +0000"/>
                            <attachment id="13081" name="error.txt.gz" size="102012" author="verthezpw" created="Mon, 19 Jun 2017 07:50:53 +0000"/>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                            <customfield id="customfield_11400" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                        <customfield id="customfield_10208" key="com.atlassian.jira.plugin.system.customfieldtypes:textfield">
                        <customfieldname>External issue ID</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>8711</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10201" key="com.atlassian.jira.plugin.system.customfieldtypes:url">
                        <customfieldname>External issue URL</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue><![CDATA[https://bugs.opendaylight.org/show_bug.cgi?id=8711]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10206" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Issue Type</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10300"><![CDATA[Bug]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_10204" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>ODL SR Target Milestone</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10324"><![CDATA[Carbon-SR1]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                    <customfield id="customfield_10000" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i029e7:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                </customfields>
    </item>
</channel>
</rss>