Deal with consequences of failed connections or failed sends
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- cpp
- Domain
- backend, distributed-systems, networking
Research direction
Read the agent, endpoint, heartbeater, and relayer implementations to compare how failed sends and connection errors are currently handled. Trace their broker and service connection paths first; the issue is done only after the failure consequences and reconnection or shutdown behavior are agreed and consistently implemented.
Written by the indexing model from the issue text.
Description
Several classes send messages:
- agent
- endpoint
- heartbeater
- relayer
Currently they all handle failures while attempting to send messages. But what are the consequences of such a failure? Should the service quit?
Another suggestion: if a connection problem occurs, start a thread that checks tries to connect to the broker or checks the service's connection, and kills the service if it can't find the broker.
- Dominant language
- C++
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from driplineorg/dripline-cpp
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
driplineorg/dripline-cpp#131 ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
driplineorg/dripline-cpp#121 · 2 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
driplineorg/dripline-cpp#114 ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
driplineorg/dripline-cpp#103 ·
-
Reactivate OP_RUNOpen
Difficulty 5/5 Over a week Newbie friendliness 35/100
driplineorg/dripline-cpp#102 ·
All issues in driplineorg/dripline-cpp
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
apache/rocketmq-clients#1469 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 9 days
-
自定义颜色添加为常用颜色Open
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
mg-chao/snow-apps#2227 · 2 comments ·
Maintainers usually reply within 1 day
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 83/100
Maintainers usually reply within 1 day
-
pnnx Python convert ignores fp16=False with input_shapesPossibly taken @ktz03 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Tencent/ncnn#7183 · 1 reaction ·
Maintainers usually reply within 1 day