<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Wed Feb 07 22:01:01 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>[CXX-987] Can&apos;t construct operation_exception without a server error</title>
                <link>https://jira.mongodb.org/browse/CXX-987</link>
                <project id="11980" key="CXX">C++ Driver</project>
                    <description>&lt;p&gt;As mentioned in a comment in &lt;a href=&quot;https://jira.mongodb.org/browse/CXX-986&quot; title=&quot;Invalid error handling in find_and_modify - null pointer access&quot; class=&quot;issue-link&quot; data-issue-key=&quot;CXX-986&quot;&gt;&lt;del&gt;CXX-986&lt;/del&gt;&lt;/a&gt;:&lt;br/&gt;
&amp;gt; In addition, I think the implementation of operation_exception is incomplete; _raw_server_error is stdx::optional&amp;lt;bsoncxx::document::value&amp;gt;, but there is no way to construct operation_exception without a valid bsoncxx::document::value.&lt;/p&gt;
</description>
                <environment></environment>
        <key id="307935">CXX-987</key>
            <summary>Can&apos;t construct operation_exception without a server error</summary>
                <type id="1" iconUrl="https://jira.mongodb.org/secure/viewavatar?size=xsmall&amp;avatarId=14703&amp;avatarType=issuetype">Bug</type>
                                            <priority id="3" iconUrl="https://jira.mongodb.org/images/icons/priorities/major.svg">Major - P3</priority>
                        <status id="6" iconUrl="https://jira.mongodb.org/images/icons/statuses/closed.png" description="The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.">Closed</status>
                    <statusCategory id="3" key="done" colorName="success"/>
                                    <resolution id="9">Done</resolution>
                                        <assignee username="rassi">J Rassi</assignee>
                                    <reporter username="david.golden@mongodb.com">David Golden</reporter>
                        <labels>
                    </labels>
                <created>Wed, 10 Aug 2016 14:14:20 +0000</created>
                <updated>Thu, 15 Sep 2016 01:08:12 +0000</updated>
                            <resolved>Thu, 15 Sep 2016 01:08:12 +0000</resolved>
                                    <version>3.0.1</version>
                                                    <component>API</component>
                    <component>Implementation</component>
                                        <votes>0</votes>
                                    <watches>1</watches>
                                                                                                                <comments>
                            <comment id="1384940" author="rassi@10gen.com" created="Thu, 15 Sep 2016 01:08:12 +0000"  >&lt;p&gt;The premise of this ticket is that &lt;tt&gt;mongocxx::operation_exception&lt;/tt&gt; does not have a constructor which leaves the &lt;tt&gt;_raw_server_error&lt;/tt&gt; member unset.  This premise is not correct, as the inheriting constructors &lt;tt&gt;mongocxx:operation_exception&lt;/tt&gt; declares from &lt;tt&gt;mongocxx::exception&lt;/tt&gt; all leave &lt;tt&gt;_raw_server_error&lt;/tt&gt; unset.  &lt;tt&gt;mongocxx:operation_exception&lt;/tt&gt; is actually usually constructed without a raw server error.  This is presumably due to the fact that most libmongoc methods that perform database operations (e.g. &lt;tt&gt;mongoc_collection_count()&lt;/tt&gt;, &lt;tt&gt;mongoc_collection_insert()&lt;/tt&gt;, &lt;tt&gt;mongoc_collection_rename()&lt;/tt&gt;, etc.) don&apos;t expose the raw reply document; they instead populate a &lt;tt&gt;bson_error_t*&lt;/tt&gt; out-argument in the case of error, which does not contain the raw server reply.&lt;/p&gt;

&lt;p&gt;As such, I&apos;m closing this ticket &quot;Works as Designed&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|hrdiof:</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>
                                                                                                                                                                                                                                                                    <customfield id="customfield_10557" key="com.pyxis.greenhopper.jira:gh-sprint">
                        <customfieldname>Sprint</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue id="1258">Perl/CXX 2016-09-30</customfieldvalue>

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