Skip to content
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

Fixed issue where we failed to store response from 1 or more endpoints #2513

Merged
merged 1 commit into from
Jun 25, 2018

Conversation

richard-cox
Copy link
Contributor

  • Bug was... connect multiple endpoints and the response from only one was processed and stored
  • Caused by minor bug mixed with not checking if the error object had a false error property
  • Renamed errors to errorsCheck to avoid future confusion

- Ensure that we process the repsonse from all endpoints that haven't failed
- Caused by minor bug mixed with not checking if the error object had a false error property
- Renamed `errors` to `errorsCheck` to avoid future confusion
@cfdreddbot
Copy link

Hey richard-cox!

Thanks for submitting this pull request! I'm here to inform the recipients of the pull request that you and the commit authors have already signed the CLA.

@richard-cox richard-cox self-assigned this Jun 25, 2018
@codecov
Copy link

codecov bot commented Jun 25, 2018

Codecov Report

Merging #2513 into v2-master will decrease coverage by 0.01%.
The diff coverage is 10%.

@@              Coverage Diff              @@
##           v2-master    #2513      +/-   ##
=============================================
- Coverage      70.66%   70.64%   -0.02%     
=============================================
  Files            590      590              
  Lines          24824    24824              
  Branches        5611     5611              
=============================================
- Hits           17542    17538       -4     
- Misses          7282     7286       +4

@KlapTrap KlapTrap merged commit ef9d86a into v2-master Jun 25, 2018
@irfanhabib irfanhabib deleted the fix-multi-endpoint-success branch June 28, 2018 10:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants