Skip to content
This repository has been archived by the owner on Dec 16, 2021. It is now read-only.

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

Merged
merged 1 commit into from
Jul 6, 2021
Merged

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

merged 1 commit into from
Jul 6, 2021

Conversation

jawid-h
Copy link
Contributor

@jawid-h jawid-h commented Jul 6, 2021

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:

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

For repository code-owners and collaborators only

  • I have assigned this pull request to a milestone

@jawid-h jawid-h added this to the v0.20 milestone Jul 6, 2021
@jawid-h jawid-h requested review from shumkov and shuplenkov July 6, 2021 10:01
@jawid-h jawid-h merged commit 519ff7b into v0.20-dev Jul 6, 2021
@jawid-h jawid-h deleted the fix/eai-again branch July 6, 2021 11:09
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Reviewers

@shumkov shumkov shumkov approved these changes

@shuplenkov shuplenkov Awaiting requested review from shuplenkov

Assignees
No one assigned
Labels
None yet
Milestone
v0.20
Development

Successfully merging this pull request may close these issues.
2 participants
@jawid-h @shumkov