<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 20:55:17 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-1133] Config list checking still not entirely correct</title>
                <link>https://jira.opendaylight.org/browse/YANGTOOLS-1133</link>
                <project id="10188" key="YANGTOOLS">yangtools</project>
                    <description>&lt;p&gt;In &lt;a href=&quot;https://jira.opendaylight.org/browse/YANGTOOLS-1090&quot; title=&quot;Config list checking is too aggressive&quot; class=&quot;issue-link&quot; data-issue-key=&quot;YANGTOOLS-1090&quot;&gt;&lt;del&gt;YANGTOOLS-1090&lt;/del&gt;&lt;/a&gt; the config list checking was fixed.&lt;/p&gt;

&lt;p&gt;But there is still a case where it produces a warning where it shouldn&apos;t: when the non-config list is added via an augment.   See the attached yang model, this produces the following warning:&lt;/p&gt;

&lt;p&gt;2020-09-01 16:50:29,742 INFO  &lt;span class=&quot;error&quot;&gt;&amp;#91;org.broadband_forum.obbaa.netconf.api.parser.YangParserUtilTest.main()&amp;#93;&lt;/span&gt; list.AbstractListStatementSupport (AbstractListStatementSupport.java:137) - Configuration list (&lt;a href=&quot;http://www.example.com/example2)values&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://www.example.com/example2)values&lt;/a&gt; does not define any keys in violation of RFC7950 section 7.8.2. While this is fine with OpenDaylight, it can cause interoperability issues with other systems &lt;span class=&quot;error&quot;&gt;&amp;#91;defined at /home/verthezp/tmp/odlwarning/example2.yang:11:4&amp;#93;&lt;/span&gt;&lt;/p&gt;

&lt;p&gt;Since this list is added to a container with config false, the warning should not be there.&lt;/p&gt;</description>
                <environment>&lt;p&gt;YANG parser 3.0.16&lt;/p&gt;</environment>
        <key id="33206">YANGTOOLS-1133</key>
            <summary>Config list checking still not entirely correct</summary>
                <type id="10104" iconUrl="https://jira.opendaylight.org/secure/viewavatar?size=xsmall&amp;avatarId=10303&amp;avatarType=issuetype">Bug</type>
                                            <priority id="3" iconUrl="https://jira.opendaylight.org/images/icons/priorities/major.svg">Medium</priority>
                        <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="10000">Done</resolution>
                                        <assignee username="rovarga">Robert Varga</assignee>
                                    <reporter username="verthezpw">Peter Verthez</reporter>
                        <labels>
                    </labels>
                <created>Tue, 1 Sep 2020 14:56:44 +0000</created>
                <updated>Mon, 21 Sep 2020 16:56:21 +0000</updated>
                            <resolved>Mon, 21 Sep 2020 16:56:21 +0000</resolved>
                                    <version>3.0.16</version>
                                    <fixVersion>6.0.0</fixVersion>
                    <fixVersion>4.0.14</fixVersion>
                    <fixVersion>5.0.7</fixVersion>
                                    <component>parser</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>2</watches>
                                                                                                                <comments>
                            <comment id="68633" author="rovarga" created="Mon, 21 Sep 2020 11:08:38 +0000"  >&lt;p&gt;Right, so this happens for the case of the augment itself, i.e. we need to understand that this is a not a uses-augment.&lt;/p&gt;</comment>
                    </comments>
                    <attachments>
                            <attachment id="15805" name="example.zip" size="586" author="verthezpw" created="Tue, 1 Sep 2020 14:55:21 +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_10000" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i03up3:</customfieldvalue>

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