ConduitIO / ConduitIO/conduit

The pipeline doesn't restart after the internet connection is restored.

Open
#608 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
610
Forks
63
Avg merge
12h 28m
Merged PRs (30d)
57

Description

Logs:
2022-05-23T08:11:05+00:00 ERR error processing HTTP request error="rpc error: code = FailedPrecondition desc = failed to stop pipeline: can't stop pipeline with status \"UserStopped\": pipeline not running" http_endpoint="POST /v1/pipelines/93bd204b-a545-41e1-a320-82323058d3d6/stop" request_id=a45dca90-feb0-4efd-a3e3-2c7c06ab08af stack=null

https://user-images.githubusercontent.com/102546122/186804065-45232a9c-16e1-4f05-b250-923ce4213195.mp4

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the connection-loss and restoration scenario, then trace the pipeline lifecycle around the POST /v1/pipelines/{id}/stop endpoint shown in the logs. Determine why restoration leaves the pipeline stopped or in UserStopped status; done means a pipeline resumes automatically after connectivity returns without producing the logged error.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
data-engineering
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.