Merge branch 'master' into dependabot/pip/mypy-1.19.0

Author: blink1073

.evergreen/generated_configs/functions.yml

@@ -239,6 +239,19 @@ functions:
         working_dir: src
       type: test
 
+  # Test numpy
+  test numpy:
+    - command: subprocess.exec
+      params:
+        binary: bash
+        args:
+          - .evergreen/just.sh
+          - test-numpy
+        working_dir: src
+        include_expansions_in_env:
+          - TOOLCHAIN_VERSION
+      type: test
+
   # Upload coverage
   upload coverage:
     - command: ec2.assume_role

.evergreen/generated_configs/tasks.yml

@@ -4768,6 +4768,28 @@ tasks:
       - noauth
       - pypy
 
+  # Test numpy tests
+  - name: test-numpy-python3.10
+    commands:
+      - func: test numpy
+        vars:
+          TOOLCHAIN_VERSION: "3.10"
+    tags:
+      - binary
+      - vector
+      - python-3.10
+      - test-numpy
+  - name: test-numpy-python3.14
+    commands:
+      - func: test numpy
+        vars:
+          TOOLCHAIN_VERSION: "3.14"
+    tags:
+      - binary
+      - vector
+      - python-3.14
+      - test-numpy
+
   # Test standard auth tests
   - name: test-standard-auth-v4.2-python3.10-auth-ssl-sharded-cluster
     commands:

.evergreen/generated_configs/variants.yml

@@ -621,3 +621,42 @@ buildvariants:
       - rhel87-small
     expansions:
       STORAGE_ENGINE: inmemory
+
+  # Test numpy tests
+  - name: test-numpy-rhel8
+    tasks:
+      - name: .test-numpy
+    display_name: Test Numpy RHEL8
+    run_on:
+      - rhel87-small
+    tags: [binary, vector, pr]
+  - name: test-numpy-macos
+    tasks:
+      - name: .test-numpy
+    display_name: Test Numpy macOS
+    run_on:
+      - macos-14
+    tags: [binary, vector]
+  - name: test-numpy-macos-arm64
+    tasks:
+      - name: .test-numpy
+    display_name: Test Numpy macOS Arm64
+    run_on:
+      - macos-14-arm64
+    tags: [binary, vector]
+  - name: test-numpy-win64
+    tasks:
+      - name: .test-numpy
+    display_name: Test Numpy Win64
+    run_on:
+      - windows-64-vsMulti-small
+    tags: [binary, vector]
+  - name: test-numpy-win32
+    tasks:
+      - name: .test-numpy
+    display_name: Test Numpy Win32
+    run_on:
+      - windows-64-vsMulti-small
+    expansions:
+      IS_WIN32: "1"
+    tags: [binary, vector]

.evergreen/scripts/generate_config.py

@@ -339,6 +339,37 @@ def create_disable_test_commands_variants():
     return [create_variant(tasks, display_name, host=host, expansions=expansions)]
 
 
+def create_test_numpy_tasks():
+    tasks = []
+    for python in MIN_MAX_PYTHON:
+        tags = ["binary", "vector", f"python-{python}", "test-numpy"]
+        task_name = get_task_name("test-numpy", python=python)
+        test_func = FunctionCall(func="test numpy", vars=dict(TOOLCHAIN_VERSION=python))
+        tasks.append(EvgTask(name=task_name, tags=tags, commands=[test_func]))
+    return tasks
+
+
+def create_test_numpy_variants() -> list[BuildVariant]:
+    variants = []
+    base_display_name = "Test Numpy"
+
+    # Test a subset on each of the other platforms.
+    for host_name in ("rhel8", "macos", "macos-arm64", "win64", "win32"):
+        tasks = [".test-numpy"]
+        host = HOSTS[host_name]
+        tags = ["binary", "vector"]
+        if host_name == "rhel8":
+            tags.append("pr")
+        expansions = dict()
+        if host_name == "win32":
+            expansions["IS_WIN32"] = "1"
+        display_name = get_variant_name(base_display_name, host)
+        variant = create_variant(tasks, display_name, host=host, tags=tags, expansions=expansions)
+        variants.append(variant)
+
+    return variants
+
+
 def create_oidc_auth_variants():
     variants = []
     for host_name in ["ubuntu22", "macos", "win64"]:
@@ -1140,6 +1171,14 @@ def create_run_tests_func():
     return "run tests", [setup_cmd, test_cmd]
 
 
+def create_test_numpy_func():
+    includes = ["TOOLCHAIN_VERSION"]
+    test_cmd = get_subprocess_exec(
+        include_expansions_in_env=includes, args=[".evergreen/just.sh", "test-numpy"]
+    )
+    return "test numpy", [test_cmd]
+
+
 def create_cleanup_func():
     cmd = get_subprocess_exec(args=[".evergreen/scripts/cleanup.sh"])
     return "cleanup", [cmd]

.evergreen/scripts/setup_tests.py

@@ -1,12 +1,10 @@
 from __future__ import annotations
 
 import base64
-import io
 import os
 import platform
 import shutil
 import stat
-import tarfile
 from pathlib import Path
 from urllib import request
 
@@ -117,9 +115,10 @@ def setup_libmongocrypt():
     LOGGER.info(f"Fetching {url}...")
     with request.urlopen(request.Request(url), timeout=15.0) as response:  # noqa: S310
         if response.status == 200:
-            fileobj = io.BytesIO(response.read())
-        with tarfile.open("libmongocrypt.tar.gz", fileobj=fileobj) as fid:
-            fid.extractall(Path.cwd() / "libmongocrypt")
+            with Path("libmongocrypt.tar.gz").open("wb") as f:
+                f.write(response.read())
+            Path("libmongocrypt").mkdir()
+            run_command("tar -xzf libmongocrypt.tar.gz -C libmongocrypt")
     LOGGER.info(f"Fetching {url}... done.")
 
     run_command("ls -la libmongocrypt")

.github/pull_request_template.md

@@ -1,38 +1,33 @@
 <!-- Thanks for contributing! -->
 <!-- Please ensure that the title of the PR is in the following form:
-[Issue Type]-[Issue Key]: Issue Title
+[JIRA TICKET]: Issue Title
 
 If you are an external contributor and there is no JIRA ticket associated with your change, then use your best judgement
 for the PR title. A MongoDB employee will create a JIRA ticket and edit the name and links as appropriate.
+
+Note on AI Contributions:
+We do not accept pull requests that are primarily or substantially generated by AI tools (ChatGPT, Copilot, etc.).
+All contributions must be written and understood by human contributors.
 -->
-[Issue Key](https://jira.mongodb.org/browse/%7BISSUE_KEY%7D)
-## Summary
-<!-- What conceptually is this PR introducing? If context is already provided from the JIRA ticket, still place it in the
-Pull Request as you should not make the reviewer do digging for a basic summary. -->
+[JIRA TICKET]
 
 ## Changes in this PR
 <!-- What changes did you make to the code? What new APIs (public or private) were added, removed, or edited to generate
 the desired outcome explained in the above summary? -->
 
-## Testing Plan
+## Test Plan
 <!-- How did you test the code? If you added unit tests, you can say that. If you didn’t introduce unit tests, explain why.
 All code should be tested in some way – so please list what your validation strategy was. -->
 
-### Screenshots (optional)
-<!-- Usually a great supplement to a test plan, especially if this requires local testing. -->
-
 ## Checklist
 <!-- Do not delete the items provided on this checklist. -->
+
 ### Checklist for Author
 - [ ] Did you update the changelog (if necessary)?
-- [ ] Is the intention of the code captured in relevant tests?
-- [ ] If there are new TODOs, has a related JIRA ticket been created?
+- [ ] Is there test coverage?
+- [ ] Is any followup work tracked in a JIRA ticket? If so, add link(s).
 
-### Checklist for Reviewer {@primary_reviewer}
+### Checklist for Reviewer
 - [ ] Does the title of the PR reference a JIRA Ticket?
 - [ ] Do you fully understand the implementation? (Would you be comfortable explaining how this code works to someone else?)
-- [ ] Have you checked for spelling & grammar errors?
 - [ ] Is all relevant documentation (README or docstring) updated?
-
-## Focus Areas for Reviewer (optional)
-<!-- List any complex portion of code you believe needs additional scrutiny and explain why. -->

.github/workflows/zizmor.yml

@@ -18,4 +18,4 @@ jobs:
         with:
           persist-credentials: false
       - name: Run zizmor 🌈
-        uses: zizmorcore/zizmor-action@b0e5c0b2b3785bc67b9b6c743fdbd495cda1b4c4
+        uses: zizmorcore/zizmor-action@c0e2b1c877e25a91d1d747c438d49199cad29698

CONTRIBUTING.md

@@ -387,6 +387,11 @@ If you are running one of the `no-responder` tests, omit the `run-server` step.
 To run any of the test suites with minimum supported dependencies, pass `--test-min-deps` to
 `just setup-tests`.
 
+## Testing time-dependent operations
+
+- `test.utils_shared.delay` - One can trigger an arbitrarily long-running operation on the server using this delay utility
+  in combination with a `$where` operation. Use this to test behaviors around timeouts or signals.
+
 ## Adding a new test suite
 
 - If adding new tests files that should only be run for that test suite, add a pytest marker to the file and add