You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: Docs/reference/content/reference/driver/error_handling.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,7 +22,7 @@ There are a few types of errors you will see.
22
22
Even when some servers are available, it might not be possible to satisfy a request. For example, using [tag sets]({{< docsref "core/read-preference/#tag-sets" >}}) in a read preference when no server exists with those tags or attempting to write to a [replica set]({{< docsref "core/replication-introduction/" >}}) when the Primary is unavailable. Both of these would result in a [`TimeoutException`]({{< msdnref "system.timeoutexception" >}}). Below is an example exception (formatted for readability) when attempting to insert into a replica set without a primary.
23
23
24
24
```bash
25
-
System.TimeoutException: A timeout occured after 30000ms selecting a server using
25
+
System.TimeoutException: A timeout occurred after 30000ms selecting a server using
26
26
CompositeServerSelector{
27
27
Selectors =
28
28
WritableServerSelector,
@@ -79,7 +79,7 @@ If you are having trouble discovering why the driver can't connect, [enabling ne
79
79
When a server is not listening at the location specified, the driver can't connect to it.
80
80
81
81
```bash
82
-
System.TimeoutException: A timeout occured after 30000ms selecting a server using
82
+
System.TimeoutException: A timeout occurred after 30000ms selecting a server using
83
83
CompositeServerSelector{
84
84
Selectors =
85
85
WritableServerSelector,
@@ -116,7 +116,7 @@ Fixing this problem either involves starting a server at the specified location
116
116
When DNS is misconfigured, or the hostname provided is not registered, resolution from hostname to IP address may fail.
117
117
118
118
```bash
119
-
System.TimeoutException: A timeout occured after 30000ms selecting a server using
119
+
System.TimeoutException: A timeout occurred after 30000ms selecting a server using
120
120
CompositeServerSelector{
121
121
Selectors =
122
122
WritableServerSelector,
@@ -160,7 +160,7 @@ DNS problems might be seen when a replica set is misconfigured. It is imperative
160
160
When the latency between the driver and the server is too great, the driver may give up.
161
161
162
162
```bash
163
-
System.TimeoutException: A timeout occured after 30000ms selecting a server using
163
+
System.TimeoutException: A timeout occurred after 30000ms selecting a server using
164
164
CompositeServerSelector{
165
165
Selectors =
166
166
WritableServerSelector,
@@ -197,7 +197,7 @@ The default connection timeout is 30 seconds and can be changed using the [`Mong
197
197
When the credentials or the authentication mechanism is incorrect, the application will fail to connect.
198
198
199
199
```bash
200
-
System.TimeoutException: A timeout occured after 30000ms selecting a server using
200
+
System.TimeoutException: A timeout occurred after 30000ms selecting a server using
201
201
CompositeServerSelector{
202
202
Selectors =
203
203
WritableServerSelector,
@@ -283,7 +283,7 @@ MongoDB.Driver.MongoBulkWriteException`1[MongoDB.Bson.BsonDocument]: A bulk writ
283
283
at MongoDB.Driver.MongoCollectionImpl`1.<BulkWriteAsync>d__11.MoveNext() in c :\projects\mongo-csharp-driver\src\MongoDB.Driver\MongoCollectionImpl.cs:line 166
284
284
```
285
285
286
-
Above, we see that a duplicate key exception occured. In this case, two writes existed in the batch. Inspected the [`WriteErrors`]({{< apiref "P_MongoDB_Driver_MongoBulkWriteException_WriteErrors" >}}) property would allow the identification of which write failed.
286
+
Above, we see that a duplicate key exception occurred. In this case, two writes existed in the batch. Inspected the [`WriteErrors`]({{< apiref "P_MongoDB_Driver_MongoBulkWriteException_WriteErrors" >}}) property would allow the identification of which write failed.
Copy file name to clipboardExpand all lines: Docs/reference/content/reference/driver_core/events.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -119,7 +119,7 @@ static void Main()
119
119
120
120
### Operation Ids
121
121
122
-
Any commands that could occur based on user initiation will contain an operation identifier. This identifer can be used to link together all events that occured due to the user initiated action.
122
+
Any commands that could occur based on user initiation will contain an operation identifier. This identifer can be used to link together all events that occurred due to the user initiated action.
Copy file name to clipboardExpand all lines: tests/MongoDB.Driver.Tests/Specifications/client-side-encryption/prose-tests/ClientEncryptionProseTests.cs
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -262,7 +262,7 @@ public void BypassSpawningMongocryptdViaMongocryptdBypassSpawnTest(
0 commit comments