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

innerring: exit if we cannot bind to the control endpoint #1643

Merged
merged 1 commit into from
Aug 4, 2022

Conversation

fyrchik
Copy link
Contributor

@fyrchik fyrchik commented Jul 30, 2022

Close #1641 .

Return listen errors in a synchronous fashion.
Another solution would be to use buffered channel, but this is not
scalable: for each new similar runner we would need to extend the
buffer.

Signed-off-by: Evgenii Stratonikov evgeniy@morphbits.ru

@codecov
Copy link

codecov bot commented Jul 30, 2022

Codecov Report

❗ No coverage uploaded for pull request base (master@0a60524). Click here to learn what that means.
The diff coverage is n/a.

❗ Current head a2027c3 differs from pull request most recent head d91566b. Consider uploading reports for the commit d91566b to get more accurate results

@@            Coverage Diff            @@
##             master    #1643   +/-   ##
=========================================
  Coverage          ?   33.18%           
=========================================
  Files             ?      332           
  Lines             ?    22706           
  Branches          ?        0           
=========================================
  Hits              ?     7536           
  Misses            ?    14552           
  Partials          ?      618           

📣 Codecov can now indicate which changes are the most critical in Pull Requests. Learn more

@carpawell
Copy link
Member

Does that bug also mean that if we somehow got some errors almost simultaneously, we won't stop the app due to the unbuffered err channel?

KirillovDenis
KirillovDenis previously approved these changes Aug 4, 2022
realloc
realloc previously approved these changes Aug 4, 2022
carpawell
carpawell previously approved these changes Aug 4, 2022
…point

Return listen errors in a synchronous fashion.
Another solution would be to use buffered channel, but this is not
scalable: for each new similar runner we would need to extend the
buffer.

Signed-off-by: Evgenii Stratonikov <evgeniy@morphbits.ru>
@carpawell carpawell merged commit 9a5f9d6 into nspcc-dev:master Aug 4, 2022
@alexchetaev alexchetaev added the U3 Regular label Aug 23, 2022
aprasolova pushed a commit to aprasolova/neofs-node that referenced this pull request Oct 19, 2022
…point

Return listen errors in a synchronous fashion.
Another solution would be to use buffered channel, but this is not
scalable: for each new similar runner we would need to extend the
buffer.

Signed-off-by: Evgenii Stratonikov <evgeniy@morphbits.ru>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working U3 Regular
Projects
None yet
Development

Successfully merging this pull request may close these issues.

if control port is busy, node silently hangs
5 participants