Skip to content
This repository has been archived by the owner on Feb 4, 2022. It is now read-only.

More verbose replica set errors emission: #231

Merged
merged 1 commit into from Nov 16, 2017
Merged

Conversation

durran
Copy link
Member

@durran durran commented Nov 5, 2017

When a replica set topology has an invalid name, core emits an error
stating that no primary or secondary found in the replica set, which can
cause some user confusion. This simply expands the language to include
that the name may be invalid to help with debugging.

When a replica set topology has an invalid name, core emits an error
stating that no primary or secondary found in the replica set, which can
cause some user confusion. This simply expands the language to include
that the name may be invalid to help with debugging.
@durran durran requested a review from mbroadst November 5, 2017 09:04
@daprahamian daprahamian merged commit de6d220 into 2.0 Nov 16, 2017
daprahamian added a commit that referenced this pull request Nov 16, 2017
daprahamian added a commit that referenced this pull request Nov 16, 2017
Port of #231 to 3.0.0.
When a replica set topology has an invalid name, core emits an error
stating that no primary or secondary found in the replica set, which can
cause some user confusion. This simply expands the language to include
that the name may be invalid to help with debugging.
mbroadst pushed a commit that referenced this pull request Nov 20, 2017
Port of #231 to 3.0.0.
When a replica set topology has an invalid name, core emits an error
stating that no primary or secondary found in the replica set, which can
cause some user confusion. This simply expands the language to include
that the name may be invalid to help with debugging.
@mbroadst mbroadst deleted the cryptic-message branch January 10, 2018 00:24
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
2 participants