Sends the START_ASSET_TRANSFER_MSG through the same channel as the UPDATE_ASSET_TRANSFER_MSG
#3886
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #3853
Identify the Bug or Feature request
As discussed in #3853, sometimes a client can get stuck during the download of a campaign.
Description of the Change
Following the suggestion from @sauliuskarmanovas, we send the
START_ASSET_TRANSFER_MSGon the same channel as theUPDATE_ASSET_TRANSFER_MESSAGEto prevent that the messages referring to the same asset are received from the client in the wrong order.Possible Drawbacks
None foreseen
Tests done
Documentation Notes
N/A
Release Notes
This change is