Skip to content

Conversation

@csfmomo
Copy link
Contributor

@csfmomo csfmomo commented Feb 22, 2020

What this PR does / why we need it:
Added endpoint checking logic before calling consecutiveAdd. If endpoint is attached, return directly without calling consecutiveAdd.
When endpoint is attached, it means ADD has been done successfully previously. No consecutiveAdd is needed.

Which issue this PR fixes
fixes #367

@csfmomo csfmomo changed the title [DO-NOT-MERGE] Fix unnecessary consecutiveAdd for windows Fix unnecessary consecutiveAdd for windows Feb 26, 2020
@csfmomo
Copy link
Contributor Author

csfmomo commented Feb 26, 2020

Test is finished and it generated logs which proved this CR change is expected.

Copy link
Contributor

@jaer-tsun jaer-tsun left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@csfmomo csfmomo merged commit 2ecca21 into master Feb 26, 2020
@csfmomo csfmomo deleted the fixAddForWindows branch March 3, 2020 20:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Optimize attach endpoint for repetitive ADD calls

3 participants