fix: EAI_AGAIN error code was not handled in a client - Githubissues

dashevo / dapi

DEPRECATED A decentralized API for the Dash network

MIT License

17 stars 11 forks source link

fix: EAI_AGAIN error code was not handled in a client #381

Closed jawid-h closed 3 years ago

jawid-h commented 3 years ago

Issue being fixed or feature implemented

Due to the nature of Docker a DNS error may occur on an early start of DAPI container leading to EAI_AGAIN error

What was done?

EAI_AGAIN error code being handled with reconnect logic

How Has This Been Tested?

Local setup

Breaking Changes

None.

Checklist:

[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have added or updated relevant unit/integration/functional/e2e tests
[x] I have made corresponding changes to the documentation

For repository code-owners and collaborators only

[x] I have assigned this pull request to a milestone