Known Issues
5279 tracked MongoDB server issues from Jira with status, affected versions, and resolution details.
NODE-7459ClosedFixed
TLS connections lose TCP keepAlive after NODE-6245
Customer report: [https://jira.mongodb.org/browse/HELP-89527]
Environment: AWS Lambda (Node 20.x, 15-minute timeout), MongoDB Data Federation (Atlas) via AWS PrivateLink. Long-running `$out` aggregation into S3.
Timelines
6.15 (6.16 would work the same):
* CommandStarted, aggregation
* Data Federation completes in ~6 min
* CommandSucceeded, aggregation
6.17:
* CommandStarted, aggregation
* Data Federation completes in ~6 min
* ...
* Lambda timeout (15 min)
Components
CMAPConnection Layer
Affected Versions
6.17.06.18.06.19.06.20.07.0.06.21.07.1.0
Fixed Versions
7.1.1
SERVER-137177ClosedFixed
Select WiredTiger Windows checksum implementation under clang-cl
Windows cross builds with clang-cl define both GNU and MSVC architecture macros, which selects two WiredTiger x86 checksum implementations. Select the Windows intrinsic implementation in `src/third_party/wiredtiger/BUILD.bazel` and add CRC32C regression vectors covering seeds, alignment, trailing bytes, and incremental checksums.
Extracted from #63670. Targets master independently of #64507 and uses the cross-platform selector already merged in #64056. Native build flags are unchanged.
Components
WiredTiger
Fixed Versions
9.1.0-rc09.1.0-rc1025
CSHARP-5956ClosedDone
Add test variant for the Secure Frontend Processor (monguard)
This ticket was split from {{DRIVERS-3395}}, please see that ticket for a detailed description.
Components
Authentication
Fixed Versions
4.0.0
GODRIVER-4125Ready for Work
Test and document that GridFSBucket.OpenDownloadStream is goroutine-safe
h3. *Context*
Currently the Go Driver {{GridFSBucket.OpenDownloadStream}} method is goroutine-safe, but it's not documented or tested. We should test that {{GridFSBucket.OpenDownloadStream}} is goroutine-safe and say it's goroutine-safe in the documentation.
h3. *Definition of done*
* Add a test that calls {{GridFSBucket.OpenDownloadStream}} in different goroutines and asserts that the uploaded results are correct.
** Also test {{GridFSBucket.OpenDownloadStreamByName}} with a similar test.
GODRIVER-4123Ready for Work
Make GridFS OpenUploadStream and UploadFromStream goroutine-safe
h3. *Context*
Currently the Go Driver {{GridFSBucket.OpenUploadStream}} method is not goroutine-safe. While we don't explicitly document that the GridFS API is goroutine safe, it's surprising to users because the Go Driver CRUD API is goroutine-safe and there's no technical reason that the GridFS API shouldn't be goroutine-safe.
We should make {{GridFSBucket.OpenUploadStream}} goroutine-safe.
h3. *Definition of done*
{{OpenUploadStream}}
* Add a test that calls {{GridFSBucket.OpenUpl
GODRIVER-4129Ready for Work
Test and document that GridFSBucket.Drop is goroutine-safe
h3. *Context*
Currently the Go Driver {{GridFSBucket.Drop}} method is goroutine-safe, but it's not documented or tested. We should test that {{GridFSBucket.Drop}} is goroutine-safe and say it's goroutine-safe in the documentation.
h3. *Definition of done*
* Add a test that calls {{GridFSBucket.Drop}} in different goroutines and asserts that the uploaded results are correct.
** Previous testing shows that method is likely already goroutine-safe.
** See a proof-of-concept test generated by
GODRIVER-4127Ready for Work
Test and document that GridFSBucket.Find is goroutine-safe
Test and document that GridFSBucket.Find is goroutine-safe
h3. *Context*
Currently the Go Driver {{GridFSBucket.Find}} method is goroutine-safe, but it's not documented or tested. We should test that {{GridFSBucket.Find}} is goroutine-safe and say it's goroutine-safe in the documentation.
h3. *Definition of done*
* Add a test that calls {{GridFSBucket.Find}} in different goroutines and asserts that the uploaded results are correct.
** Previous testing shows that method is likely alread
GODRIVER-3841Ready for Work
gridfs has a data race (found by go test -race)
h3. *Context*
When running the test suite for [https://github.com/chirino/memory-service]
I ran into the following data race in the mongo driver. I've now put in a mutex around calls to the mongo driver, which is not ideal. See the attached datarace.log for more details about the race.
h3. *Definition of done*
{color:#505f79}You should run your unit test/integration tests with *go test -race* {color}
{color:#505f79}that may allow you to reproduce this.{color}
h3. *Pitfalls*
{c
Components
GridFS
Affected Versions
2.5.0
GODRIVER-4126Ready for Work
Test and document that GridFSBucket.DownloadToStream is goroutine-safe
Test and document that GridFSBucket.DownloadToStream is goroutine-safe
h3. *Context*
Currently the Go Driver {{GridFSBucket.DownloadToStream}} method is goroutine-safe, but it's not documented or tested. We should test that {{GridFSBucket.DownloadToStream}} is goroutine-safe and say it's goroutine-safe in the documentation.
h3. *Definition of done*
* Add a test that calls {{GridFSBucket.DownloadToStream}} in different goroutines and asserts that the uploaded results are correct.
** Als
GODRIVER-4131Ready for Work
Remove dead code from GridFSBucket
h3. *Context*
GridFSBucket.writeBuf is no longer used and shuld be removed
h3. *Definition of done*
See context
h3. *Pitfalls*
Not investigated
GODRIVER-4065Ready for Work
Unskip tests for version 7.0 on release/2.8 or 2.9
Unskip tests changed in GODRIVER-4064.
GODRIVER-4128Ready for Work
Test and document that GridFSBucket.Rename is goroutine-safe
h3. *Context*
Currently the Go Driver {{GridFSBucket.Rename}} method is goroutine-safe, but it's not documented or tested. We should test that {{GridFSBucket.Rename}} is goroutine-safe and say it's goroutine-safe in the documentation.
h3. *Definition of done*
* Add a test that calls {{GridFSBucket.Rename}} in different goroutines and asserts that the uploaded results are correct.
** Previous testing shows that method is likely already goroutine-safe.
** See a proof-of-concept test generat
GODRIVER-3214Backlog
ErrTransactInProgress is returned after using the same session from a previously failed txn
h3. Detailed steps to reproduce the problem?
Mongosync ran into a "transaction already in progress" error. Looking at the code, mongosync only ever calls session.WithTransaction() a second time with the same session as the first call if the first returned an error. From this convo https://mongodb.slack.com/archives/C7WJZNUTA/p1715012926709339 and this comment in [WithTransaction|https://github.com/mongodb/mongo-go-driver/blob/6a53da6ddea3bf1cfb835ac22e33a85416051429/mongo/session.go#L223] it lo
GODRIVER-3547Backlog
Use gofmt for internal/assert/difflib_test.go
gofmt - 99%
From Go Report Card: Gofmt formats Go programs. We run {{gofmt -s}} on your code, where {{-s}} is for the ["simplify" command|https://golang.org/cmd/gofmt/#hdr-The_simplify_command]
* [internal/assert/difflib_test.go|https://goreportcard.com/report/go.mongodb.org/mongo-driver]
** [Line 1|https://goreportcard.com/report/go.mongodb.org/mongo-driver#L1]: warning: file is not gofmted with -s (gofmt)
See here: [https://goreportcard.com/report/go.mongodb.org/mongo-driver]
(gocyc
GODRIVER-3464Needs Triage
Enable memento for capturing slack threads in JIRA comments
h3. *Context*
[Memento|https://wiki.corp.mongodb.com/display/~thomas.langston@mongodb.com/Memento+Slack+App] is a Slack app lets you copy thread contents to a JIRA issue.
h3. *Definition of done*
* Enable the app for the #go-driver channel
* Add Memento to the GODRIVER project: [https://github.com/10gen/iteng-memento/blob/main/docs/memento/onboarding.md]
GODRIVER-3497ClosedDeclined
Strip newline in web identity token file if found
h3. *Context*
Tracking [PR #1965|https://github.com/mongodb/mongo-go-driver/pull/1965]
h3. *Definition of done*
{color:#505f79}What must be done to consider the task complete?{color}
h3. *Pitfalls*
{color:#505f79}What should the implementer watch out for? What are the risks?{color}
GODRIVER-1983Backlog
Migrate all Spec Tests to The Unified Test Runner
{panel:title=Epic Summary|borderStyle=dashed|borderColor=#ccc|titleBGColor=#239eb0|bgColor=#c2d2c2}
*Summary*
Complete the migration of all spec tests to the new format.
*Motivation*
We won't get the full benefit of the unified format while we still have other formats.
h4. Cast of Characters
Engineering Lead:
Document Author:
POCers:
Product Owner:
Program Manager:
Stakeholders:
h4. Documentation
[Scope Document|some.url]
[Technical Design Document|some.url]
{panel}
GODRIVER-3563Backlog
Add testdata/README.md
h3. *Context*
Now that we use git submodules for tesdata/specifications it would be helpful to add a README.md file explaining how to use the repository for local development. Additionally, we should include brief explanations for each subdirectory that is not part of the submodule (client-side-encryption-prose, extended_bson, kmip-certs, and monogcrypt).
h3. *Definition of done*
Add a README.md file to testdata with the following sections:
* How to initialize the specifications sub
NODE-7942ClosedDuplicate
[VERCEL AI SDK] Product Security LRA items
*Context:* Launch Readiness Assessment flagged Security as Yellow. Complete these before GA. Moved from PRODUCT-1918.
*Tasks*
* *SSDLC baseline:* Complete the SSDLC baseline for the package (threat model, security review, documented controls).
* *Release signing:* Sign published npm tarballs and artifacts in the release pipeline.
* *Vulnerability scanning:* Onboard the repo to the DevProd Vulnerability Scanning platform for third-party dependency scanning.
* *Papertrail:* Integrate re
Components
ABX