-
Notifications
You must be signed in to change notification settings - Fork 168
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RCORE-2150 Include originating client reset error message when reporting auto client reset failures #7761
Conversation
Pull Request Test Coverage Report for Build michael.wilkersonbarker_1135Details
💛 - Coveralls |
@@ -408,7 +408,7 @@ class SyncSession : public std::enable_shared_from_this<SyncSession> { | |||
|
|||
void download_fresh_realm(const sync::SessionErrorInfo& error_info) | |||
REQUIRES(!m_config_mutex, !m_state_mutex, !m_connection_state_mutex); | |||
void handle_fresh_realm_downloaded(DBRef db, StatusWith<sync::SessionErrorInfo> error_info, | |||
void handle_fresh_realm_downloaded(DBRef db, Status result, const sync::SessionErrorInfo& cr_error_info, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why did this change back?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Because I needed access to both the Status
that just occurred as well as the SessionErrorInfo
for the originating client reset error. When it was using the StatusWith
, you would only have access to one or the other...
What, How & Why?
The originating client reset error was not included in the error reported to the client as part of the changes from #7649. This PR adds the originating client reset error to the error message included with the
AutoClientResetFailed
error reported to the client.Fixes #7760
☑️ ToDos
* [ ] C-API, if public C++ API changed* [ ]bindgen/spec.yml
, if public C++ API changed