<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Thu Feb 08 08:37:29 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>MongoDB Jira</title>
    <link>https://jira.mongodb.org</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>9.7.1</version>
        <build-number>970001</build-number>
        <build-date>13-04-2023</build-date>
    </build-info>


<item>
            <title>[GODRIVER-1945] Improved error messages</title>
                <link>https://jira.mongodb.org/browse/GODRIVER-1945</link>
                <project id="14289" key="GODRIVER">Go Driver</project>
                    <description>&lt;p&gt;Currently, the error messages that can result from socket problems reading a server&apos;s response are confusing. For example, this one&lt;br/&gt;
&lt;a href=&quot;https://github.com/mongodb/mongo-go-driver/blob/ea02175e9e44795efdda597ebd94b11d746d3984/x/mongo/driver/topology/connection.go#L470&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/mongo-go-driver/blob/ea02175e9e44795efdda597ebd94b11d746d3984/x/mongo/driver/topology/connection.go#L470&lt;/a&gt;&lt;br/&gt;
can result in a message like &quot;incomplete read of message header&quot; for a context of &quot;read tcp 192.168.248.6:38030-&amp;gt;192.168.248.6:27000: i/o timeout&quot; in response to a socket timeout expiring.  This message isn&apos;t accurate because this particular function call is reading more than a message header, and because &quot;incomplete&quot; incorrectly implies at least one message header byte was successfully read.  Driver consumers should not need to know these items of detail anyway.&lt;/p&gt;

&lt;p&gt;Instead, to make error diagnosis easier for driver consumers, can we change the error messages in this function to be something like &quot;socket error reading server response&quot;?  The context that gets appended to this message should have sufficient further detail already.&lt;/p&gt;</description>
                <environment></environment>
        <key id="1667218">GODRIVER-1945</key>
            <summary>Improved error messages</summary>
                <type id="4" iconUrl="https://jira.mongodb.org/secure/viewavatar?size=xsmall&amp;avatarId=14710&amp;avatarType=issuetype">Improvement</type>
                                            <priority id="4" iconUrl="https://jira.mongodb.org/images/icons/priorities/minor.svg">Minor - P4</priority>
                        <status id="10038" iconUrl="https://jira.mongodb.org/images/icons/subtask.gif" description="">Backlog</status>
                    <statusCategory id="2" key="new" colorName="default"/>
                                    <resolution id="-1">Unresolved</resolution>
                                        <assignee username="-1">Unassigned</assignee>
                                    <reporter username="milkie@mongodb.com">Eric Milkie</reporter>
                        <labels>
                    </labels>
                <created>Wed, 31 Mar 2021 20:27:06 +0000</created>
                <updated>Wed, 30 Mar 2022 23:43:43 +0000</updated>
                                                                            <component>Error Handling</component>
                                        <votes>0</votes>
                                    <watches>2</watches>
                                                                                                                <comments>
                            <comment id="3709888" author="milkie" created="Fri, 9 Apr 2021 12:54:30 +0000"  >&lt;p&gt;We could use that wording, but it&apos;s still not useful for driver consumers, only for driver developers with access to the source code.  An expected error in this location is &quot;socket timeout&quot; (and there is an implied mitigation for users if they see this phrasing); any other errors such as only 2 bytes read would be unexpected and there would be no user mitigation for that other than to talk to MongoDB engineering.&lt;/p&gt;</comment>
                            <comment id="3709326" author="divjot.arora" created="Fri, 9 Apr 2021 02:07:29 +0000"  >&lt;p&gt;The specific error message mentioned in the ticket is returned specifically when there&apos;s an error reading the first four bytes of a wire message, which contain the full length of the message. The &quot;incomplete read of message header&quot; wording is awkward because it&apos;s not clear what &quot;incomplete&quot; means and the phrase &quot;message header&quot; may not be obvious for a user of the driver. We can update this to something like &quot;error reading first four length bytes of the server response&quot;.&lt;/p&gt;</comment>
                    </comments>
                    <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_15850" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_12550" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>2|hynpk7:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10558" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>9223372036854775807</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            </customfields>
    </item>
</channel>
</rss>