ECLK / ECLK/Results-Dist

Subscriber needs to recognize when it has missed a result and be able to get missing ones

Open
#21 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
Ballerina
Stars
13
Forks
7
PR merge metrics
No merged PRs in 30d

Description

For various reasons, the subscriber may not get all the results. In that case, it should be able to detect that and go get a particular result number.

Contributor guide

No contributing guide indexed for this repository

Research direction

The issue names no files, tests, or entry points. Start by locating the subscriber's result-handling path and the mechanism that identifies result numbers, then clarify how missed results should be detected and retrieved before implementation; done means a subscriber can recognize a gap and request a particular missing result.

Written by the indexing model from the issue text.

Assessment

Domain
distributed-systems
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.