<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Wed Feb 07 22:00:33 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-849] Audit API usage of int32_t</title>
                <link>https://jira.mongodb.org/browse/CXX-849</link>
                <project id="11980" key="CXX">C++ Driver</project>
                    <description>&lt;p&gt;We should review usages of int32_t in the API and ensure that they are correct. In particular, things like pipeline::skip or pipeline::sample. Another example is places where we are specifying a base fixed size integer for enumerations. Is this actually needed? Or should we let it default to int? Changing integer sizes is a common source of ABI breaks so we should make sure we are doing the right thing out of the gate.&lt;/p&gt;</description>
                <environment></environment>
        <key id="266732">CXX-849</key>
            <summary>Audit API usage of int32_t</summary>
                <type id="3" iconUrl="https://jira.mongodb.org/secure/viewavatar?size=xsmall&amp;avatarId=14718&amp;avatarType=issuetype">Task</type>
                                            <priority id="3" iconUrl="https://jira.mongodb.org/images/icons/priorities/major.svg">Major - P3</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="andrew.morrow@mongodb.com">Andrew Morrow</reporter>
                        <labels>
                    </labels>
                <created>Fri, 19 Feb 2016 13:18:34 +0000</created>
                <updated>Wed, 8 Feb 2023 18:52:28 +0000</updated>
                                                                            <component>API</component>
                                        <votes>0</votes>
                                    <watches>3</watches>
                                                                                                                <comments>
                            <comment id="1297418" author="david.golden" created="Fri, 17 Jun 2016 00:48:10 +0000"  >&lt;p&gt;Code review for std::chrono::duration checks: &lt;a href=&quot;https://github.com/mongodb/mongo-cxx-driver/pull/500&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/mongo-cxx-driver/pull/500&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="1295408" author="david.golden" created="Wed, 15 Jun 2016 16:38:40 +0000"  >&lt;p&gt;I think for these we always take std::chrono, so we can just do a runtime check that the values fit in int32_t rather than an int64_t as I had been planning to do.  Practically speaking, I doubt we&apos;ll see larger values in real-world code.  If libmongoc changes and if we get user demand for astronomically high maxTimeMS values, then we can consider changing the runtime check.&lt;/p&gt;</comment>
                            <comment id="1295074" author="acm" created="Wed, 15 Jun 2016 14:09:32 +0000"  >&lt;p&gt;We should probably correct our API and then deal with overflow at runtime internally at the site where we call the C driver. That way we don&apos;t leak this implementation flaw out to our consumers, and can eventually address it once the C driver updates ABI and we can depend on that version as our minimum. It might be tricky during the transition if we need to support both ABIs, but presumably we can interrogate the function for the size of its argument, either at configure time or via some clever template hackery.&lt;/p&gt;</comment>
                            <comment id="1295048" author="david.golden" created="Wed, 15 Jun 2016 13:59:45 +0000"  >&lt;p&gt;libmongoc restricts maxTimeMS and maxAwaitTimeMS to int32_t in some places, whereas the spec calls for int64_t. (Filed as &lt;a href=&quot;https://jira.mongodb.org/browse/CDRIVER-1329&quot; title=&quot;maxTimeMS and maxAwaitTimeMS should be Int64, not Int32&quot; class=&quot;issue-link&quot; data-issue-key=&quot;CDRIVER-1329&quot;&gt;CDRIVER-1329&lt;/a&gt;)&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10012">
                    <name>Related</name>
                                            <outwardlinks description="related to">
                                        <issuelink>
            <issuekey id="294103">CDRIVER-1329</issuekey>
        </issuelink>
                            </outwardlinks>
                                                                <inwardlinks description="is related to">
                                        <issuelink>
            <issuekey id="382649">CXX-1338</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <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_10857" key="com.pyxis.greenhopper.jira:gh-epic-link">
                        <customfieldname>Epic Link</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>CXX-1569</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_21553" key="com.atlassian.jira.plugin.system.customfieldtypes:labels">
                        <customfieldname>Quarter</customfieldname>
                        <customfieldvalues>
                                        <label>FY24Q1</label>
    
                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_12550" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>2|hr1k1p:ft</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="1244">Platforms 2016-09-19</customfieldvalue>

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