Lets not forget to create an issue to handle failure here
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 5
- Forks
- 6
- Avg merge
- 3h 52m
- Merged PRs (30d)
- 1
Description
Lets not forget to create an issue to handle failure here
Originally posted by @MeirShpilraien in https://github.com/RedisGears/LibMR/pull/54#discussion_r1869065805
Contributor 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.
Research direction
Start by reading the failure-handling discussion quoted from pull request #54 and identify which failure scenario it refers to in LibMR. The issue does not name a file, test, entry point, or expected behavior, so the failure case and acceptance criteria must be clarified before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, redis
- Domain
- backend, data
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100