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

🐛 The dataservice throws 500 if gen3 does #197

Merged
merged 1 commit into from
Mar 23, 2019
Merged

Conversation

fiendish
Copy link
Contributor

@fiendish fiendish commented Mar 22, 2019

Gen3 throws internal errors if you ask it to walk and chew gum at the same time.
Then the dataservice forwards the 500 status, which basically kills GF endpoint access until kids-first/kf-api-dataservice#487 gets fixed.

Gen3 throws internal errors if you ask it to walk and chew gum at the same time. 
Then dataservice forwards the 500 status, which basically kills GF endpoint access until kids-first/kf-api-dataservice#487 gets fixed.
@fiendish fiendish requested a review from znatty22 March 22, 2019 19:14
@fiendish
Copy link
Contributor Author

Fixes #196

Copy link
Member

@znatty22 znatty22 left a comment

Choose a reason for hiding this comment

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

In general we should prob try to avoid putting stuff that pertains to a particular use of the library (target service = dataservice) into the library code itself. I think this change is small and probably fine so why not

@fiendish
Copy link
Contributor Author

The motivation was specific, but I do think that retrying a few times on a status 500 is probably the right thing to do anyway.

@fiendish fiendish merged commit c35ab8c into master Mar 23, 2019
@znatty22 znatty22 deleted the gen3-500-retry branch March 25, 2019 19:00
@znatty22 znatty22 added the feature New functionality label Apr 17, 2019
@znatty22 znatty22 mentioned this pull request Apr 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New functionality
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants