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

error handling for read ETIMEDOUT error #2846

Open
wants to merge 13 commits into
base: v6/develop
Choose a base branch
from

Conversation

milosstanisavljevic
Copy link
Contributor

@milosstanisavljevic milosstanisavljevic commented Dec 25, 2023

Description

Added addition error handling that would potentially solve read ETIMEDOUT error

Fixes # (issue)

Type of change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

  • Test A
  • Test B

Checklist:

  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged and published in downstream modules

src/controllers/rpc/publish-rpc-controller.js Outdated Show resolved Hide resolved
src/service/operation-id-service.js Outdated Show resolved Hide resolved
{ errorMessage: 'Unable to handle request' },
);
this.logger.error(
`Error handling message from ${peerIdString} to ${this.config.id}: protocol :${protocol} with operationId${message.header.operationId} and keyword:${message.header.keywordUuid}, Error : ${error} `,
Copy link
Collaborator

Choose a reason for hiding this comment

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

Please update log messages to be consistent everywhere in PR, they should have following format word: ${value}, so some word, semi-colons followed by space and after that a value

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.

5 participants