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

Fix timing issues with rapid protocol calls and missing dynamodb database fetch calls #68

Merged
merged 4 commits into from Feb 9, 2020

Conversation

nenti
Copy link
Contributor

@nenti nenti commented Feb 6, 2020

When running locally on a very powerful machine like the one used in continuous integration the calls coming from the graphql client of:

  1. $connect
  2. $default -> gql_connect
  3. $default -> gql_start

Can be quicker in the handler than the createConnection entry dynamodb call is taking to complete. This results into unexpected errors in the connection for local test runs and potentially also on production.

I fixed this by adding a retry mechanism to the connection hydration that is used for the initial call so it retrys once when the connection is not found.

@nenti
Copy link
Contributor Author

nenti commented Feb 6, 2020

This fixes #67

@michalkvasnicak
Copy link
Owner

Thank you very much @nenti, released as 1.0.0-alpha.3. Also I added you to contributors list.

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.

None yet

2 participants