<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 20:53:55 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-655] Error parsing enums with unknown substatements inside its values</title>
                <link>https://jira.opendaylight.org/browse/YANGTOOLS-655</link>
                <project id="10188" key="YANGTOOLS">yangtools</project>
                    <description>&lt;p&gt;Please consider the following YANG excerpt:&lt;/p&gt;

&lt;p&gt;    grouping gigabit-eth-mdix {&lt;br/&gt;
        leaf mdix {&lt;/p&gt;

&lt;p&gt;            tailf:info &quot;Configure MDIX mode&quot;;&lt;br/&gt;
            mandatory true;&lt;br/&gt;
            tailf:cli-suppress-no;&lt;/p&gt;

&lt;p&gt;            type enumeration {&lt;br/&gt;
                enum normal &lt;/p&gt;
{
                    tailf:info &quot;Set interface MDIX to Normal mode&quot;;
                }
&lt;p&gt;                enum xover &lt;/p&gt;
{
                    tailf:info &quot;Set interface MDIX to X-Over mode&quot;;
                }
&lt;p&gt;                enum auto &lt;/p&gt;
{
                    tailf:info &quot;Set interface MDIX to Automatic Detection mode&quot;;
                }
&lt;p&gt;            }&lt;br/&gt;
        }&lt;br/&gt;
    }&lt;/p&gt;

&lt;p&gt;When debugging what was being parsed, I encountered this problem:&lt;/p&gt;

&lt;p&gt;All &quot;tailf&quot; statements (which are considered Unknown Statements) were at at the Leaf level. Although each enum value have a property for unknown statements aswell, they are all empty as you can see in the attached file.&lt;/p&gt;

&lt;p&gt;I would expect that for this example, only&lt;/p&gt;

&lt;p&gt;            tailf:info &quot;Configure MDIX mode&quot;;&lt;br/&gt;
            tailf:cli-suppress-no;&lt;/p&gt;

&lt;p&gt;should be considered unknown statements of &quot;leaf mdix&quot;. The rest, should be inside the collection of unkown statements of its repective enum value IMO.&lt;/p&gt;</description>
                <environment>&lt;p&gt;Operating System: All&lt;br/&gt;
Platform: All&lt;/p&gt;</environment>
        <key id="23075">YANGTOOLS-655</key>
            <summary>Error parsing enums with unknown substatements inside its values</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="10001">Won&apos;t Do</resolution>
                                        <assignee username="-1">Unassigned</assignee>
                                    <reporter username="patrickthiagobard@gmail.com">Patrick Thiago Bard</reporter>
                        <labels>
                    </labels>
                <created>Mon, 29 Aug 2016 11:45:55 +0000</created>
                <updated>Sun, 10 Apr 2022 18:35:51 +0000</updated>
                            <resolved>Sun, 5 Mar 2017 14:24:16 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>2</watches>
                                                                                                                <comments>
                            <comment id="44066" author="patrickthiagobard@gmail.com" created="Mon, 29 Aug 2016 11:45:55 +0000"  >&lt;p&gt;Attachment yang-tools-debugging-unknown-statements.txt has been added with description: debugging unknown statements&lt;/p&gt;</comment>
                            <comment id="44062" author="ifoltin" created="Wed, 31 Aug 2016 08:03:37 +0000"  >&lt;p&gt;Hello Patrick,&lt;/p&gt;

&lt;p&gt;I did some testing and this issue only appears in the old yang parser, which was removed in boron.&lt;br/&gt;
Try using the new yang parser (that was introduced in beryllium release).&lt;br/&gt;
Here is a documentation which explains how to use the new parser (see section &quot;Working with YANG Model&quot;):&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://github.com/opendaylight/yangtools/blob/master/docs/src/main/asciidoc/developer/introduction.adoc&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/opendaylight/yangtools/blob/master/docs/src/main/asciidoc/developer/introduction.adoc&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="44063" author="patrickthiagobard@gmail.com" created="Tue, 6 Sep 2016 12:26:43 +0000"  >&lt;p&gt;Strange, because in our project we are using the following maven dependency&lt;/p&gt;

&lt;p&gt;    &amp;lt;dependency&amp;gt;&lt;br/&gt;
        &amp;lt;groupId&amp;gt;org.opendaylight.yangtools&amp;lt;/groupId&amp;gt;&lt;br/&gt;
        &amp;lt;artifactId&amp;gt;yang-parser-impl&amp;lt;/artifactId&amp;gt;&lt;br/&gt;
        &amp;lt;version&amp;gt;0.8.3-Beryllium-SR3&amp;lt;/version&amp;gt;&lt;br/&gt;
    &amp;lt;/dependency&amp;gt;&lt;/p&gt;</comment>
                            <comment id="44064" author="ifoltin" created="Tue, 6 Sep 2016 13:42:06 +0000"  >&lt;p&gt;Well, the old yang parser is still there in the beryllium release, it was removed later in the boron release. So could you please try using the new one according to the instructions I posted here earlier.&lt;/p&gt;</comment>
                            <comment id="44065" author="rovarga" created="Sun, 5 Mar 2017 14:24:16 +0000"  >&lt;p&gt;Old vs. new parser is a matter of instantiation, CrossSourceStatementReactor is the entrypoint to the new one.&lt;/p&gt;

&lt;p&gt;Since this affects desupported codebase with a replacement, closing as WONTFIX.&lt;/p&gt;</comment>
                    </comments>
                    <attachments>
                            <attachment id="13059" name="yang-tools-debugging-unknown-statements.txt" size="1822" author="patrickthiagobard@gmail.com" created="Mon, 29 Aug 2016 11:45:55 +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>6561</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=6561]]></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_10000" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i028kf:</customfieldvalue>

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