Update m_flx_active_version when an QUERY_ERROR occurs

[sync-by-unito]

The handle role change project updated the operation of subscriptions such that if a server-initiated bootstrap was started while a subscription was being bootstrapped, the subscription will be reset to the Pending state and the m_flx_last_seen_version will be reset to the m_flx_active_version value.

There was a comment posted on PR #7675, which contained this change, regarding updating the m_flx_last_seen_version when a sync session starts or when a subscription QUERY_ERROR occurs and possibly updating the validation in the SessionWrapper::on_flx_sync_progress() function regarding this value.

Since this change could have potential side effects with progress notifications which relies on the m_flx_active_version value, it was pulled out into a separate task to isolate and investigate these changes.

[sync-by-unito]

➤ PM Bot commented:

Jira ticket: RCORE-2173

[sync-by-unito]

➤ Jonathan Reams commented:

[~[email protected]], tracking the active version has all been reworked in 819bb98, so is this still a valid thing to do?

[sync-by-unito]

➤ michael-wb commented:

Correct - these variables have been removed and this request is no longer valid.