Add support for server selection's deprioritized servers to all topologies. by vbabanin · Pull Request #1860 · mongodb/mongo-java-driver

vbabanin · 2026-01-12T21:06:22Z

Relevant specification changes:

DRIVERS-3344 - Add support for server selection's deprioritized servers to all topologies (#1865)
DRIVERS-3380 Filter deprioritized candidates by address only (#1886)
DRIVERS-3404 - Server selection deprioritization only for overload errors on replica sets (#1900) - the change has not yet been addressed in this PR, because it was introduced after creation of the PR; requires us to return the condition we had previously, but change it and either introduce it in a different place, or attach additional information to a deprioritized server address.
DRIVERS-3406 test deprioritized selection with tag sets (#1903) - the change has not yet been addressed in this PR, because it was introduced after creation of the PR.

JAVA-6021,
JAVA-6074,
JAVA-6105,
JAVA-6114

…ogies. JAVA-6021

stIncMale · 2026-01-12T22:34:56Z

driver-core/src/main/com/mongodb/internal/connection/BaseCluster.java


-    protected void updateDescription(final ClusterDescription newDescription) {
+    @VisibleForTesting(otherwise = PROTECTED)
+    public void updateDescription(final ClusterDescription newDescription) {


It seems we can avoid making this method public by overriding it in the subclass. We won't even need to make it public in the subclass, because the test code using the method will be in the same package as the subclass. However, this requires the subclass to not be anonymous (if we could use var, the proposed approach would have worked even for an anonymous subclass).

vbabanin · 2026-01-17T21:27:13Z

driver-core/src/test/unit/com/mongodb/connection/ServerSelectionSelectionTest.java

+        } catch (MongoTimeoutException mongoTimeoutException) {
+            List<ServerDescription> inLatencyWindowServers = buildServerDescriptions(definition.getArray("in_latency_window"));
+            assertTrue("Expected emtpy but was " + inLatencyWindowServers.size() + " " + definition.toJson(
+                    JsonWriterSettings.builder()
+                            .indent(true).build()), inLatencyWindowServers.isEmpty());
+            return;


Since we now perform the full server-selection path (via BaseCluster), the behavior of "no servers selected: is observed differently than before.

Previously, these tests invoked the Selector directly, got an empty list, and asserted on that result. With BaseCluster, server selection runs the normal selection loop: it will retry until either a server becomes selectable or the selection timeout elapses.

In this setup, a server selection timeout is the expected signal that no servers are available/eligible for selection. The timeout is set to 200ms to keep the test fast, while giving enough headroom to avoid any flakiness.

vbabanin · 2026-01-17T21:41:57Z

driver-core/src/test/unit/com/mongodb/connection/ServerSelectionSelectionTest.java

-        List<ServerDescription> latencyBasedSelectedServers = latencyBasedServerSelector.select(clusterDescription);
-        assertServers(latencyBasedSelectedServers, inLatencyWindowServers);
+        assertNotNull(serverTuple);
+        assertTrue(inLatencyWindowServers.stream().anyMatch(s -> s.getAddress().equals(serverTuple.getServerDescription().getAddress())));


There’s an ambiguity in the server selection spec docs about what drivers must assert for in_latency_window:

tests/README.md says to verify the set of servers in in_latency_window.

"Drivers implementing server selection MUST test that their implementation correctly returns the set of servers in in_latency_window."

server-selection-tests.mdsays to verify the selection returns one of the servers in in_latency_window.

"Drivers implementing server selection MUST test that their implementations correctly return one of the servers in in_latency_window."

This test follows server-selection-tests.md, so asserting that the selected server is within the expected in_latency_window set is consistent with the requirements in the spec.

P.S: Both files were created in this single commit with contradicting requirements:

Feb 6, 2015 - Commit 6b63123a - "Add Server Selection Spec" File 1: server-selection-tests.rst Drivers implementing server selection MUST test that their implementations correctly return one of the servers in ``in_latency_window``. File 2: tests/README.rst Drivers implementing server selection MUST test that their implementations correctly return the set of servers in ``in_latency_window``.

# Conflicts: # driver-core/src/test/resources/specifications # driver-core/src/test/unit/com/mongodb/connection/ServerSelectionSelectionTest.java

stIncMale

The last reviewed commit is f20b482.

The files I haven't yet reviewed:

ServerDeprioritizationTest
ServerSelectionSelectionTest

@vbabanin I am proposing to resolve all the outstanding comments before proceeding with the changes required by DRIVERS-3404 (for details, see the description of this PR).

stIncMale · 2026-02-10T08:28:16Z

driver-core/src/test/functional/com/mongodb/ClusterFixture.java

-            new ReadConcernAwareNoOpSessionContext(ReadConcern.DEFAULT),
-            new TimeoutContext(TIMEOUT_SETTINGS),
-            getServerApi());
+    public static OperationContext getOperationContext() {


Thank you for noticing the issue with OperationContext being mutable (it was mutable before this PR), and fixing it.

The methods returning OperationContext in this class are a mess:

getOperationContext()

createOperationContext(TimeoutSettings timeoutSettings)

createNewOperationContext(TimeoutSettings timeoutSettings)

getOperationContext(ReadPreference readPreference)

Let's name the methods consistently. I think, all of the aforementioned methods should use the "create" prefix.
1.1. Let's do this automatically via IDE in a separate commit, and express in the commit message that the commit was done via automatic refactoring, so that reviewers know not to review it.

Let's remove the weirdly named and trivial createNewOperationContext method, and inline it where it is used (fortunately, it is used only in two places in ClusterFixture, and nowhere else).

Done in:

103c4b0

021c262

stIncMale · 2026-02-10T09:03:25Z

driver-core/src/test/functional/com/mongodb/connection/ConnectionSpecification.groovy

-        def source = getBinding().getReadConnectionSource(OPERATION_CONTEXT)
-        def connection = source.getConnection(OPERATION_CONTEXT)
+        def source = getBinding().getReadConnectionSource(getOperationContext())
+        def connection = source.getConnection(getOperationContext())


I think, the OperationContext used here should be the same. There may be many more changed places in this PR where this is the case, and given how many changes there are, it may not be too easy to identify them all.

For brevity, I'll be marking such places with just the "same context" comment. For now I am not sure if it is even practically achievable to identify them all.

The problem is exacerbated by ClusterFixture creating a new OperationContext each time it needs one, which means that the ClusterFixture.getBinding never uses the same context as the one used by the test calling ClusterFixture.getBinding.

Done in: 4310894
Identified one more place: c736e6a

stIncMale · 2026-02-10T09:11:04Z

driver-core/src/test/functional/com/mongodb/connection/ConnectionSpecification.groovy

-        def source = getBinding().getReadConnectionSource(OPERATION_CONTEXT)
-        def connection = source.getConnection(OPERATION_CONTEXT)
+        def source = getBinding().getReadConnectionSource(getOperationContext())
+        def connection = source.getConnection(getOperationContext())


same context

Done in: 4310894

stIncMale · 2026-02-10T19:35:10Z

.../src/test/unit/com/mongodb/internal/connection/AbstractServerDiscoveryAndMonitoringTest.java

@@ -98,7 +98,7 @@ protected void applyApplicationError(final BsonDocument applicationError) {
        switch (type) {
            case "command":
                exception = getCommandFailureException(applicationError.getDocument("response"), serverAddress,
-                        OPERATION_CONTEXT.getTimeoutContext());
+                        getOperationContext().getTimeoutContext());


same context

Done in: 4310894

stIncMale · 2026-02-10T19:49:30Z

driver-core/src/test/unit/com/mongodb/internal/connection/ServerDiscoveryAndMonitoringTest.java

+            Timeout serverSelectionTimeout = getOperationContext().getTimeoutContext().computeServerSelectionTimeout();
            DefaultServer server = (DefaultServer) getCluster()
-                    .getServersSnapshot(serverSelectionTimeout, OPERATION_CONTEXT.getTimeoutContext())
+                    .getServersSnapshot(serverSelectionTimeout, getOperationContext().getTimeoutContext())


same context

Done in: 4310894

stIncMale · 2026-02-11T17:25:10Z

driver-core/src/main/com/mongodb/internal/connection/BaseCluster.java

-                final ClusterableServerFactory serverFactory,
-                final ClientMetadata clientMetadata) {
+    @VisibleForTesting(otherwise = PRIVATE)
+    protected BaseCluster(final ClusterId clusterId,


The value of otherwise is incorrect here.

Done in: 08b3466

stIncMale · 2026-02-11T17:34:29Z

driver-core/src/main/com/mongodb/internal/connection/BaseCluster.java

                getRaceConditionPreFilteringSelector(serversSnapshot),
-                serverSelector,
-                serverDeprioritization.getServerSelector(),
+                serverDeprioritization.applyDeprioritization(serverSelector),


Let's rename the method to apply. The name of the type (ServerDeprioritization) of the object whose instance method we call tells what is being applied. There is no need to duplicate that in the names of methods.

Let's do this automatically via IDE in a separate commit, and express in the commit message that the commit was done via automatic refactoring, so that reviewers know not to review it.

Done in: 98caa34

stIncMale · 2026-02-12T02:08:50Z

driver-core/src/main/com/mongodb/internal/connection/OperationContext.java

+                if (serverDescriptions.size() == 1 || deprioritized.isEmpty()) {
+                    return wrappedSelector.select(clusterDescription);
                }
+
                List<ServerDescription> nonDeprioritizedServerDescriptions = serverDescriptions
                        .stream()
                        .filter(serverDescription -> !deprioritized.contains(serverDescription.getAddress()))
                        .collect(toList());


Let's leave a TODO-JAVA-XXXX comment linking this code (the if optimization as well as the use of Stream) to the existing performance ticket about server selection. We should also mention in the description of that ticket that there are TODO-JAVA-XXXX comments that needs to be addressed.

The open questions here are:

whether the if optimization is worth itl

whether we should use a loop instead of using Stream.

Done in:
a6587fa
c97cb65
012aa6b

stIncMale · 2026-02-12T02:24:36Z

driver-core/src/main/com/mongodb/internal/connection/OperationContext.java

+                        new ClusterDescription(clusterDescription.getConnectionMode(), clusterDescription.getType(),
+                                nonDeprioritizedServerDescriptions,
+                                clusterDescription.getClusterSettings(),
+                                clusterDescription.getServerSettings()));


We should use the

public ClusterDescription(final ClusterConnectionMode connectionMode, final ClusterType type, @Nullable final MongoException srvResolutionException, final List<ServerDescription> serverDescriptions, @Nullable final ClusterSettings clusterSettings, @Nullable final ServerSettings serverSettings) {

constructor.

driver-core/src/main/com/mongodb/internal/connection/OperationContext.java

stIncMale · 2026-03-02T08:22:12Z

I thought I already proposed this, but looks like I didn't: let's not implement any new spec changes in the PR (there were spec changes) until we resolve all outstanding discussions.

stIncMale

The last reviewed commit is f20b482.

I reviewed ServerDeprioritizationTest.java.
ServerSelectionSelectionTest.java is yet to be reviewed.

stIncMale · 2026-03-02T21:35:15Z

driver-core/src/test/unit/com/mongodb/internal/connection/ServerDeprioritizationTest.java

+                of(Named.of(generateArgumentName(ALL_SERVERS), ALL_SERVERS))
+        );
+    }
+    @ParameterizedTest


An empty line is missing after the selectNoneDeprioritized method and the @ParameterizedTest annotation on the next method.

Done in: 2bc1b2e

driver-core/src/test/unit/com/mongodb/internal/connection/ServerDeprioritizationTest.java

stIncMale · 2026-03-02T21:46:31Z

driver-core/src/test/unit/com/mongodb/internal/connection/ServerDeprioritizationTest.java

+        ServerSelector selector = createAssertingSelector(ALL_SERVERS, singletonList(SERVER_A));
+        assertEquals(singletonList(SERVER_A), serverDeprioritization.applyDeprioritization(selector).select(SHARDED_CLUSTER));


Let's return ALL_SERVERS from selector in onAttemptFailureIgnoresIfPoolClearedException. This way, we will not only check that the input to selector has all servers (that is, serverDeprioritization does not filter anything out at that point), but also that the serverDeprioritization does not have any unexpected logic of filtering the servers selected by the wrapped selector. If it had such an unexpected logic, it would have been more likely to leave SERVER_A be when it is the only server selected by the wrapped selector, and less likely to leave SERVER_A be when it is one of the servers selected by the wrapped selector. Thus, implementing selector such that it selects more than just SERVER_A, makes the test stronger.

Suggested change

ServerSelector selector = createAssertingSelector(ALL_SERVERS, singletonList(SERVER_A));

assertEquals(singletonList(SERVER_A), serverDeprioritization.applyDeprioritization(selector).select(SHARDED_CLUSTER));

ServerSelector selector = createAssertingSelector(ALL_SERVERS, ALL_SERVERS);

assertEquals(ALL_SERVERS, serverDeprioritization.applyDeprioritization(selector).select(SHARDED_CLUSTER));

Done in: 8a8bf0a.

stIncMale

The last reviewed commit is f20b482.

Everything has been reviewed.

stIncMale · 2026-03-03T00:35:04Z

driver-core/src/test/unit/com/mongodb/connection/ServerSelectionSelectionTest.java

@@ -59,6 +80,14 @@ public class ServerSelectionSelectionTest {
    private final ClusterDescription clusterDescription;
    private final long heartbeatFrequencyMS;


[this comment is not about the current PR]

Let's remove the heartbeatFrequencyMS field and make it a local variable, as Idea suggests?

Done in: cf5c484

stIncMale · 2026-03-03T00:37:24Z

driver-core/src/test/unit/com/mongodb/connection/ServerSelectionSelectionTest.java

-        try {
-            serverSelector = getServerSelector();
-            selectedServers = serverSelector.select(clusterDescription);
+        assumeTrue(!description.endsWith("/max-staleness/tests/ReplicaSetWithPrimary/MaxStalenessWithModePrimary.json"));


Why was this line changed? It seemed fine before. It is still OK now, but it now has a negation that is not necessary.

Ah, this wasn’t intentional. The assumeTrue(!...) form is the older variant (it exists on 5.5.x/5.6.x and pre-cleanup main). We later switched main to assumeFalse(...) in 41ca107. This branch was created before that change, and I likely reintroduced the old form during a merge of main into this PR.

I have updated it to assumeFalse(...) here to match main and remove the negation. Commit: 32609f6

stIncMale · 2026-03-03T14:04:51Z

driver-core/src/test/unit/com/mongodb/connection/ServerSelectionSelectionTest.java

 import static org.junit.Assert.fail;
-import static org.junit.Assume.assumeFalse;
+import static org.junit.Assume.assumeTrue;
+import static org.junit.jupiter.api.Assertions.assertNotNull;


Let's either keep using JUnit 4, or rewrite this class to use JUnit 5.

Done in: 7d3d862

stIncMale · 2026-03-03T14:06:23Z

driver-core/src/test/unit/com/mongodb/connection/ServerSelectionSelectionTest.java

+import static org.junit.jupiter.api.Assertions.assertNotNull;
+import static org.mockito.Mockito.when;

 // See https://github.com/mongodb/specifications/tree/master/source/server-selection/tests


[this comment is not about the current PR]

Let's convert this comment to a class documentation comment.

Let's change the link to https://github.com/mongodb/specifications/tree/master/source/server-selection/tests/server_selection, because the current link is misleading.

Done in: eff9e23

stIncMale · 2026-03-03T14:08:39Z

driver-core/src/test/unit/com/mongodb/connection/ServerSelectionSelectionTest.java

    private final ClusterDescription clusterDescription;
    private final long heartbeatFrequencyMS;
    private final boolean error;
+    private final List<ServerAddress> deprioritizedServerAddresses;


It does not seem that we need this field. We can call extractDeprioritizedServerAddresses from createOperationContext, which is simpler than using the deprioritizedServerAddresses instance field to pass the result of extractDeprioritizedServerAddresses to createOperationContext.

Done in: 78d685d

stIncMale · 2026-03-03T14:31:01Z

driver-core/src/test/unit/com/mongodb/connection/ServerSelectionSelectionTest.java

+    private OperationContext createOperationContext() {
+        OperationContext operationContext =
+                OperationContext.simpleOperationContext(
+                        new TimeoutContext(TIMEOUT_SETTINGS.withServerSelectionTimeoutMS(SERVER_SELECTION_TIMEOUT_MS)));


Let's use 0 ("immediate" timeout) and remove the SERVER_SELECTION_TIMEOUT_MS constant:

Suggested change

new TimeoutContext(TIMEOUT_SETTINGS.withServerSelectionTimeoutMS(SERVER_SELECTION_TIMEOUT_MS)));

new TimeoutContext(TIMEOUT_SETTINGS.withServerSelectionTimeoutMS(0)));

Done in: b16bfb0

stIncMale · 2026-03-03T14:38:50Z

driver-core/src/test/unit/com/mongodb/connection/ServerSelectionSelectionTest.java

+        OperationContext.ServerDeprioritization serverDeprioritization = operationContext.getServerDeprioritization();
+        for (ServerAddress address : deprioritizedServerAddresses) {
+            serverDeprioritization.updateCandidate(address);
+            serverDeprioritization.onAttemptFailure(new MongoConfigurationException("test"));


While not being important, MongoConfigurationException is quite a weird exception here: why would we deprioritize a server due to a client configuration exception? Of course, in production it does not matter, because such an exception does not trigger a retry. But for the sake of making this less surprising, let's use something else, like MongoException?

Done in: a7fc3fc

driver-core/src/test/unit/com/mongodb/connection/ServerSelectionSelectionTest.java

stIncMale · 2026-03-03T14:40:29Z

driver-core/src/test/unit/com/mongodb/connection/ServerSelectionSelectionTest.java

+    private BaseCluster createTestCluster(final ClusterDescription clusterDescription, final Cluster.ServersSnapshot serversSnapshot) {
+        return new TestCluster(clusterDescription, serversSnapshot);
+    }


What is the purpose of this method?

P.S. If it is really needed, it should be static.

Done in: 1d15a73

stIncMale · 2026-03-03T14:52:10Z

driver-core/src/test/unit/com/mongodb/connection/ServerSelectionSelectionTest.java

+        @Override
+        public void onChange(final ServerDescriptionChangedEvent event) {
+            // We do not expect this to be called during server selection.
+            Assertions.fail();


Does this comment communicate something that is not already obvious? It seems the assertion makes it clear that we don't expect the method to be called.

We should call com.mongodb.assertions.Assertions.fail here instead of a JUnit assertion method: we do not check that the onChange is not called, we simply do not expect the onChange method to be called on this test double, so we don't care to implement it, and that's why we simply fail (it's the same behavior we have in MongoMockito, and we use com.mongodb.assertions.Assertions.fail there, see InsufficientStubbingDetector.answer).

Done in: 3e2c0cd

…Context.java Co-authored-by: Valentin Kovalenko <valentin.male.kovalenko@gmail.com>

…onSelectionTest.java Co-authored-by: Valentin Kovalenko <valentin.male.kovalenko@gmail.com>

…erDeprioritizationTest.java Co-authored-by: Valentin Kovalenko <valentin.male.kovalenko@gmail.com>

Add support for server selection's deprioritized servers to all topol…

282bf57

…ogies. JAVA-6021

stIncMale reviewed Jan 12, 2026

View reviewed changes

Remove global OperationContext in tests as it has mutable state.

cb8905c

vbabanin self-assigned this Jan 15, 2026

vbabanin added 4 commits January 14, 2026 23:43

Merge branch 'main' into JAVA-6021

74ae21f

Merge branch 'main' into JAVA-6021

f39b7a0

Add more test-cases.

2a4cd70

Fix static checks.

fa35dd9

vbabanin commented Jan 17, 2026

View reviewed changes

Allow invoking connect.

7b613e4

vbabanin marked this pull request as ready for review January 19, 2026 22:31

vbabanin requested a review from a team as a code owner January 19, 2026 22:31

vbabanin requested a review from stIncMale January 19, 2026 22:31

nhachicha mentioned this pull request Jan 28, 2026

JAVA-5949 preserve connection pool on backpressure errors when establishing connections #1854

Closed

vbabanin added 2 commits February 9, 2026 23:17

Merge branch 'main' into JAVA-6021

7e30f2a

# Conflicts: # driver-core/src/test/resources/specifications # driver-core/src/test/unit/com/mongodb/connection/ServerSelectionSelectionTest.java

Bump specification commit.

f20b482

stIncMale requested changes Feb 25, 2026

View reviewed changes

stIncMale requested changes Mar 2, 2026

View reviewed changes

stIncMale requested changes Mar 3, 2026

View reviewed changes

vbabanin and others added 9 commits March 4, 2026 14:45

Update driver-core/src/main/com/mongodb/internal/connection/Operation…

09f24dd

…Context.java Co-authored-by: Valentin Kovalenko <valentin.male.kovalenko@gmail.com>

Update driver-core/src/test/unit/com/mongodb/connection/ServerSelecti…

733ee91

…onSelectionTest.java Co-authored-by: Valentin Kovalenko <valentin.male.kovalenko@gmail.com>

Update driver-core/src/test/unit/com/mongodb/connection/ServerSelecti…

f324ab9

…onSelectionTest.java Co-authored-by: Valentin Kovalenko <valentin.male.kovalenko@gmail.com>

Use "create" prefix consistently.

103c4b0

Remove craeteNewOperationContext.

021c262

Change visibility modifier.

08b3466

Rename applyDeprioritization method to apply.

98caa34

Add TODO comments for performance optimization.

a6587fa

Add empty line.

2bc1b2e

vbabanin and others added 27 commits March 4, 2026 18:48

Return ALL_SERVERS from selector.

8a8bf0a

Make heartbeatFrequencyMS a local variable.

cf5c484

Revert to assumeFalse.

32609f6

Use Junit4.

7d3d862

Convert comment to a class documentation comment.

eff9e23

Remove deprioritizedServerAddresses field.

78d685d

Move inLatencyWindowServers to pre-try.

ff279de

Remove unnecessary symbol.

2f06765

Add assertion context.

cdee4fa

Remove redundant comment.

12ceda7

Use immediate timeout.

b16bfb0

Use MongoException instead of MongoConfigurationException.

a7fc3fc

Remove createTestCluster method.

1d15a73

Use com.mongodb.assertions.Assertions.fail for a Fake cluster.

3e2c0cd

Change message.

9a84fc0

Update driver-core/src/test/unit/com/mongodb/internal/connection/Serv…

36c83c3

…erDeprioritizationTest.java Co-authored-by: Valentin Kovalenko <valentin.male.kovalenko@gmail.com>

Use MongoMockito.

9b81ebd

Remove TODO.

2df4580

Use withNewServerDeprioritization.

db936a1

Make ServerDeprioritization private.

64dd4f4

Remove unused methods.

cd67117

Reuse OperationContext.

4310894

Use a documentation comment.

f57616d

Use VisibleForTesting(otherwise = PROTECTED).

0a4f04f

Reuse OperatioContext.

c736e6a

Change comments.

c97cb65

Change comments.

012aa6b

vbabanin requested a review from stIncMale March 5, 2026 04:33

vbabanin added 2 commits March 4, 2026 20:33

Merge branch 'main' into JAVA-6021

471cadb

Use createOperationContext.

6767707

		ServerSelector selector = createAssertingSelector(ALL_SERVERS, singletonList(SERVER_A));
		assertEquals(singletonList(SERVER_A), serverDeprioritization.applyDeprioritization(selector).select(SHARDED_CLUSTER));

		@@ -59,6 +80,14 @@ public class ServerSelectionSelectionTest {
		private final ClusterDescription clusterDescription;
		private final long heartbeatFrequencyMS;

	new TimeoutContext(TIMEOUT_SETTINGS.withServerSelectionTimeoutMS(SERVER_SELECTION_TIMEOUT_MS)));
	new TimeoutContext(TIMEOUT_SETTINGS.withServerSelectionTimeoutMS(0)));

Conversation

vbabanin commented Jan 12, 2026 • edited by stIncMale Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

vbabanin Jan 17, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

vbabanin Jan 17, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

stIncMale left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

stIncMale Feb 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

stIncMale Feb 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

stIncMale Feb 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

stIncMale Feb 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

stIncMale commented Mar 2, 2026

Uh oh!

stIncMale left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

stIncMale left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

vbabanin commented Jan 12, 2026 •

edited by stIncMale

Loading

vbabanin Jan 17, 2026 •

edited

Loading

vbabanin Jan 17, 2026 •

edited

Loading

stIncMale Feb 10, 2026 •

edited

Loading

stIncMale Feb 10, 2026 •

edited

Loading

stIncMale Feb 10, 2026 •

edited

Loading

stIncMale Feb 10, 2026 •

edited

Loading

vbabanin Mar 4, 2026 •

edited

Loading