Known Issues
5279 tracked MongoDB server issues from Jira with status, affected versions, and resolution details.
SERVER-135984ClosedFixed
Implement aggregation pipeline equality type inference
Implement narrowType for ExpressionCompare with ExpressionCompare::EQ with two operands.
$eq: ["$a", "string"] -> makes it string(S)
$eq: ["$a", 1] -> makes it number(S)
$eq: ["$a", null] -> makes it null (or null|missing - double check the sematnics)
Whether the equality holds is given by assumeTrue, e.g.
bool equalityHolds = (expr->getOp() == ExpressionCompare::EQ) == assumeTrue;
Note:
- BSON comparison applies (equality to double(1) will match int(1), so that should just becom
Fixed Versions
9.1.0-rc09.1.0-rc1026
SERVER-138657ClosedFixed
Build the cluster key slots for streaming $group
h2. Overview
SERVER-138656 passes the group key slots as {{StreamingAggStage}}'s cluster key slots. Build the cluster key slots correctly, per the contract added in SERVER-136257.
h2. Scope of Work
* For each group key whose null and missing values may be interleaved in the input, use {{fillEmpty(k)}} as its cluster key slot; otherwise reuse the group key slot.
* {{StreamingAggStage}} accepts at most 4 such keys (tassert 13625701); with more, fall back to hash {{$group}}.
Fixed Versions
9.1.0-rc0
NODE-8009Backlog
[Mastra] Read-only index error recommends the deprecated allowWrites option
h2. TL;DR
When a write hits a read-only bring-your-own index, the error tells the user to turn on {{allowWrites: true}}. That option is now deprecated. The error should point to the supported alternatives instead.
h2. Context
{{MongoDBVector}} is Mastra's MongoDB vector store. With a _bring-your-own (BYO) collection_, Mastra searches a collection the application already owns instead of one it creates. Mastra treats these collections as read-only, so {{upsert()}}, {{updateVector()}}, {{deleteVec
Components
ABX
SERVER-138656ClosedFixed
Build StreamingAggStage from StreamingGroupNode
h2. Overview
Implement {{SlotBasedStageBuilder::buildStreamingGroup}}, building a {{StreamingAggStage}} from the {{StreamingGroupNode}} that SERVER-138655 plans.
h2. Scope of Work
* Use the group key slots as the cluster key slots.
* Stage builder unit tests.
* A jstest comparing streaming and hash {{$group}} results with the flag forced on.
h2. Notes
* The flag stays fully disabled. With the cluster key equal to the group key, results are wrong when null and missing are interleaved in the inp
Fixed Versions
9.1.0-rc09.1.0-rc1026
SERVER-139386In Code Review
Speed up Copybara history lookup and bootstrap legacy releases
Copybara startup repeatedly scanned destination history for each source commit, making legacy release syncs spend hours searching for a baseline. {{sync_repo_with_copybara.py}} now indexes destination history once while preserving the bottom-most {{GitOrigin-RevId}}, literal-space filtering, candidate ordering, and branch ancestry rules. Direct regression comparisons check old-versus-new lookup results.
Imported public history without sync trailers can bootstrap from identical reachable commits
SERVER-138625ClosedDuplicate
isSimpleIdQuery ignores extra fields
If you have a query of the form '\{_id: {a: 0, $eq: 2}}', isSimpleIdQuery in query_utils.cpp will return true and it will get sent to the express executor path where
getQueryFilterMaybeUnwrapEq will unwrap it to '\{_id: 2}' and ignore the 'a: 0' entirely. It should never get sent to the express path in the first place because isSimpleIdQuery should return false when there are multiple fields in the object.
Affected Versions
8.3.09.0.0
JAVA-6362Backlog
Request for a published OpenPGP signing-key statement for MongoDB Java Driver POMs on Maven Central
Hello,
We consume MongoDB Java Driver artifacts from Maven Central and verify the OpenPGP signature of every POM we use before accepting it. Our policy only accepts a signature when the signing key's *full fingerprint* is confirmed by an *official, public source of the publisher*.
For the coordinates below we could not find such a source:
||Coordinate||Signature created (UTC)||Key algorithm||Hash algorithm||Issuer in signature||
| {{org.mongodb:mongodb-driver-bom:5.8.1}} | 2026-07-16T1
SERVER-139152In Progress
Run compact accumulators in StreamingAggStage
Make {{StreamingAggStage}} use compact accumulators instead of {{HashAggAccumulator}}, as {{CompactHashAggStage}} does.
* Each group's states live in a pooled {{CompactStateBuffer}} that is reset in place when a group slot is reused.
SERVER-139356Needs Scheduling
updateZoneKeyRange doesn't perform hashed key range validations
[removeKeyRangeFromZone|https://github.com/10gen/mongo/blob/2de947c5f21dd4b1e676823d92f065b1bd3e2c33/src/mongo/db/global_catalog/ddl/sharding_catalog_manager_zone_operations.cpp#L389] called from updateZoneKeyRange command extends the range to the full shard key but skips [checkHashedShardKeyRange|https://github.com/10gen/mongo/blob/2de947c5f21dd4b1e676823d92f065b1bd3e2c33/src/mongo/db/global_catalog/ddl/sharding_catalog_manager_zone_operations.cpp#L169].
# Shard \{x: "hashed"} and add a zone
PYTHON-6270Ready for Work
Enable ruff rules D100-107
h3. *Context*
{color:#505f79}Describe the background behind the problem.{color}
PYTHON-6249 enabled the small number of {{D}} rules on by default. Opting into the full suite of {{D}} rules will improve docstring consistency and make enforcing our coding standards easier and more automated.
This ticket tracks the enablement of ruff rules D100-107, which check for public APIs missing docstrings.
h3. *Definition of done*
{color:#505f79}What must be done to consider the task complete?{color
Components
Infrastructure
PYTHON-6269Ready for Work
Enable ruff rule E501
h3. *Context*
{color:#505f79}Describe the background behind the problem.{color}
Ruff's [E501|https://docs.astral.sh/ruff/rules/line-too-long/] linting rule enforces the configured {{line-length}} setting for maximum line length. Our coding standards specify a maximum line length of 100 characters.
h3. *Definition of done*
{color:#505f79}What must be done to consider the task complete?{color}
Enable ruff's {{E501}} linting rule and make the required changes to pass it.
h3. *Pitfalls*
{
PYTHON-6268Ready for Work
Ruff linting expansion
{panel:borderStyle=solid|borderColor=#21313c|titleBGColor=#21313c|titleColor=#fafbfc|bgColor=#fafbfc}
h3. *Summary*
_What is the problem or use case, what are we trying to achieve?_
Expand our ruff linting rules to automatically enforce guidelines in {{CODING-STANDARDS.md}}, improve code quality and consistency, and reduce review overhead.
h3. *Motivation*
h4. Who is the affected end user?
_Who are the stakeholders?_
All contributors and reviewers in Python team projects.
h4. How d
Components
Infrastructure
PYTHON-6265Ready for Work
Opt into ruff markdown and docstring code formatting
h2. Context
PYTHON-6263 removes the blacken-docs pre-commit hook. Ruff can format Python code blocks in markdown files and code inside docstrings via {{docstring-code-format}}, but its edits are not equivalent to blacken-docs: it deletes bare {{...}} doctest continuation markers, adds blank lines inside doctest examples, and normalizes quote style in rendered examples.
h2. Definition of done
Enable markdown and docstring code formatting in pyproject, apply the one-time {{ruff format}} changes
Components
Infrastructure
PYTHON-6264Ready for Work
Enable ruff rules D205, D400, and D401
h3. *Context*
{color:#505f79}Describe the background behind the problem.{color}
PYTHON-6249 enabled the small number of {{D}} rules on by default. Opting into the full suite of {{D}} rules will improve docstring consistency and make enforcing our coding standards easier and more automated.
This ticket tracks the enablement of ruff rules D205, D400, and D401, which deal with docstring first line formatting.
h3. *Definition of done*
{color:#505f79}What must be done to consider the task co
Components
Infrastructure
PYTHON-6225Backlog
Add prose tests that a top-level error halts client bulkWrite execution (ordered and unordered)
This ticket was split from {{DRIVERS-3699}}, please see that ticket for a detailed description.
Components
CRUD & Command-Level Operations
SERVER-139360Open
Strengthen container_write_test oplog validation
{{container_write_test.cpp}} only checks that each oplog entry has the right type and parses.
Strengthen {{getNContainerInsertEntries}} to compare the oplog against the input and enforce the entry format strictly. This will cut down on code in each test, and add validation coverage.
GODRIVER-4179ClosedDone
AWS auth test cannot download MongoDB 9.0 Enterprise for Ubuntu 20.04
h3. *Context*
See [MongoDB 9.0 Enterprise Ubuntu platform support|https://www.mongodb.com/docs/manual/tutorial/install-mongodb-enterprise-on-ubuntu/].
h3. *Definition of done*
-See if we can use RHEL 8.7 for the MONGODB-AWS AUTH 9.0 tests.-
Upgrade to Ubuntu 24.04 once DRIVERS-3704 is resolved. See here for a POC: https://github.com/mongodb/mongo-go-driver/compare/master...prestonvasquez:mongo-go-driver:task/godriver-4179-aws-auth-ci-rhel-8-7
h3. *Pitfalls*
Not investigated
Fixed Versions
2.11.0
PYTHON-6150Backlog
Add test coverage for top-level error handling in multi-batch bulkWrite
This ticket was split from {{DRIVERS-3670}}, please see that ticket for a detailed description.
Components
CRUD & Command-Level Operations
PYTHON-6257ClosedGone away
Static PR checks failing to reach ubuntu archives
h3. *Name of Failure:*
Static cppcheck and Mod WSGI latest tests.
h3. *Link to task:*
https://github.com/mongodb/mongo-python-driver/actions/runs/43055799726/job/130644793090?pr=3199 and https://github.com/mongodb/mongo-python-driver/actions/runs/43055799831/job/130659564796?pr=3199.
h3. *Context of when and why the failure occurred:*
Started occurring today, Nov 11 2026.
h3. *Stack trace:*
PYTHON-6276ClosedWon't Do
Enable ruff rule ERA001
h3. *Context*
{color:#505f79}Describe the background behind the problem.{color}
Ruff's ERA001 rule forbids commented-out code. This is generally a good practice and improves codebase quality and readability.
h3. *Definition of done*
{color:#505f79}What must be done to consider the task complete?{color}
Enable rule ERA001 and make the required changes to pass it.
h3. *Pitfalls*
{color:#505f79}What should the implementer watch out for? What are the risks?{color}