From 38ab5b27302a5103178730e42e044b7e071927f8 Mon Sep 17 00:00:00 2001 From: Andreas Braun Date: Wed, 4 Jun 2025 14:24:44 +0200 Subject: [PATCH] Fix pre-commit linter errors --- source/client-side-encryption/tests/README.md | 6 ------ source/extended-json/extended-json.md | 1 - source/retryable-writes/retryable-writes.md | 1 - .../server-discovery-and-monitoring.md | 1 - source/server-discovery-and-monitoring/server-monitoring.md | 1 - .../transactions-convenient-api.md | 1 - source/transactions/tests/legacy-test-format.md | 1 - source/unified-test-format/unified-test-format.md | 1 - 8 files changed, 13 deletions(-) diff --git a/source/client-side-encryption/tests/README.md b/source/client-side-encryption/tests/README.md index 67f8748f65..b56160d62f 100644 --- a/source/client-side-encryption/tests/README.md +++ b/source/client-side-encryption/tests/README.md @@ -251,7 +251,6 @@ Then for each element in `tests`: This MAY be configured system-wide. - `tlsCertificateKeyFile` (or equivalent) set to [drivers-evergreen-tools/.evergreen/x509gen/client.pem](https://github.com/mongodb-labs/drivers-evergreen-tools/blob/master/.evergreen/x509gen/client.pem). - The method of passing TLS options for KMIP TLS connections is driver dependent. 2. If `autoEncryptOpts` does not include `keyVaultNamespace`, default it to `keyvault.datakeys`. @@ -427,7 +426,6 @@ First, perform the setup. This MAY be configured system-wide. - `tlsCertificateKeyFile` (or equivalent) set to [drivers-evergreen-tools/.evergreen/x509gen/client.pem](https://github.com/mongodb-labs/drivers-evergreen-tools/blob/master/.evergreen/x509gen/client.pem). - The method of passing TLS options for KMIP TLS connections is driver dependent. @@ -684,7 +682,6 @@ binary subtype 4 (or standard UUID), which MUST be decoded and encoded as subtyp This MAY be configured system-wide. - `tlsCertificateKeyFile` (or equivalent) set to [drivers-evergreen-tools/.evergreen/x509gen/client.pem](https://github.com/mongodb-labs/drivers-evergreen-tools/blob/master/.evergreen/x509gen/client.pem). - The method of passing TLS options for KMIP TLS connections is driver dependent. @@ -1447,7 +1444,6 @@ Four mock KMS server processes must be running: 1. The mock [KMS HTTP server](https://github.com/mongodb-labs/drivers-evergreen-tools/blob/master/.evergreen/csfle/kms_http_server.py). - Run on port 9000 with [ca.pem](https://github.com/mongodb-labs/drivers-evergreen-tools/blob/master/.evergreen/x509gen/ca.pem) as a CA @@ -1463,7 +1459,6 @@ Four mock KMS server processes must be running: 2. The mock [KMS HTTP server](https://github.com/mongodb-labs/drivers-evergreen-tools/blob/master/.evergreen/csfle/kms_http_server.py). - Run on port 9001 with [ca.pem](https://github.com/mongodb-labs/drivers-evergreen-tools/blob/master/.evergreen/x509gen/ca.pem) as a CA @@ -1479,7 +1474,6 @@ Four mock KMS server processes must be running: 3. The mock [KMS HTTP server](https://github.com/mongodb-labs/drivers-evergreen-tools/blob/master/.evergreen/csfle/kms_http_server.py). - Run on port 9002 with [ca.pem](https://github.com/mongodb-labs/drivers-evergreen-tools/blob/master/.evergreen/x509gen/ca.pem) as a CA diff --git a/source/extended-json/extended-json.md b/source/extended-json/extended-json.md index 51471e3c60..ce3dacd2b5 100644 --- a/source/extended-json/extended-json.md +++ b/source/extended-json/extended-json.md @@ -722,7 +722,6 @@ parsed as a normal document and not reported as an error. - Changed BSON binary type wrapper to `{"$binary": {"base64": , "subType": }}` - - Added "Restrictions and limitations" section. diff --git a/source/retryable-writes/retryable-writes.md b/source/retryable-writes/retryable-writes.md index 2d674ffe74..609de18b92 100644 --- a/source/retryable-writes/retryable-writes.md +++ b/source/retryable-writes/retryable-writes.md @@ -314,7 +314,6 @@ Drivers MUST then retry the operation as many times as necessary until any one o - CSOT is enabled and the operation times out per [Client Side Operations Timeout: Retryability](../client-side-operations-timeout/client-side-operations-timeout.md#retryability). - - CSOT is not enabled and one retry was attempted. diff --git a/source/server-discovery-and-monitoring/server-discovery-and-monitoring.md b/source/server-discovery-and-monitoring/server-discovery-and-monitoring.md index 15dc14617e..206e8236c3 100644 --- a/source/server-discovery-and-monitoring/server-discovery-and-monitoring.md +++ b/source/server-discovery-and-monitoring/server-discovery-and-monitoring.md @@ -240,7 +240,6 @@ Fields: Default null. (Only mongos and shard servers record this field when monitoring config servers as replica sets, at least until [drivers allow applications to use readConcern "afterOptime".](../max-staleness/max-staleness.md#future-feature-to-support-readconcern-afteroptime)) - - (=) `type`: a [ServerType](#servertype) enum value. Default Unknown. diff --git a/source/server-discovery-and-monitoring/server-monitoring.md b/source/server-discovery-and-monitoring/server-monitoring.md index d35358c21d..5f1be7fa04 100644 --- a/source/server-discovery-and-monitoring/server-monitoring.md +++ b/source/server-discovery-and-monitoring/server-monitoring.md @@ -501,7 +501,6 @@ the client MUST follow these steps: [Why synchronize clearing a server's pool with updating the topology?](server-discovery-and-monitoring.md#why-synchronize-clearing-a-servers-pool-with-updating-the-topology)). If this was a network timeout error, then the pool MUST be cleared with interruptInUseConnections = true (see [Why does the pool need to support closing in use connections as part of its clear logic?](../connection-monitoring-and-pooling/connection-monitoring-and-pooling.md#why-does-the-pool-need-to-support-interrupting-in-use-connections-as-part-of-its-clear-logic)) - 4. If this was a network error and the server was in a known state before the error, the client MUST NOT sleep and MUST begin the next check immediately. (See diff --git a/source/transactions-convenient-api/transactions-convenient-api.md b/source/transactions-convenient-api/transactions-convenient-api.md index a4a0b1a93d..7d1864391a 100644 --- a/source/transactions-convenient-api/transactions-convenient-api.md +++ b/source/transactions-convenient-api/transactions-convenient-api.md @@ -142,7 +142,6 @@ This method should perform the following sequence of actions: MaxTimeMSExpired and the elapsed time of `withTransaction` is less than 120 seconds, jump back to step eight. We will trust `commitTransaction` to apply a majority write concern on retry attempts (see: [Majority write concern is used when retrying commitTransaction](#majority-write-concern-is-used-when-retrying-committransaction)). - 2. If the `commitTransaction` error includes a "TransientTransactionError" label and the elapsed time of `withTransaction` is less than 120 seconds, jump back to step two. diff --git a/source/transactions/tests/legacy-test-format.md b/source/transactions/tests/legacy-test-format.md index 59f1e6a06d..73dc482797 100644 --- a/source/transactions/tests/legacy-test-format.md +++ b/source/transactions/tests/legacy-test-format.md @@ -182,7 +182,6 @@ Then for each element in `tests`: 7. When testing against a sharded cluster run a `distinct` command on the newly created collection on all mongoses. For an explanation see, [Why do tests that run distinct sometimes fail with StaleDbVersion?](#why-do-tests-that-run-distinct-sometimes-fail-with-staledbversion) - 8. If `failPoint` is specified, its value is a configureFailPoint command. Run the command on the admin database to enable the fail point. diff --git a/source/unified-test-format/unified-test-format.md b/source/unified-test-format/unified-test-format.md index a35503d714..f662ed2ba6 100644 --- a/source/unified-test-format/unified-test-format.md +++ b/source/unified-test-format/unified-test-format.md @@ -1307,7 +1307,6 @@ The structure of each object is as follows: When `failureIsRedacted` is present and its value is `true`, the test runner MUST assert that a failure is present and that the failure has been redacted according to the rules defined for error redaction in the [command logging and monitoring specification](../command-logging-and-monitoring/command-logging-and-monitoring.md#security). - When `false`, the test runner MUST assert that a failure is present and that the failure has NOT been redacted.