microsoft / microsoft/durabletask-netherite
Implement poison message handling
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- C#
- Stars
- 239
- Forks
- 37
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 2
Description
Observing an execution where a message got corrupted (four consecutive \0 bytes in a string) and then gets infinitely retried.
Need to
- investigate source of corruption
- consider poison message handling
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
No file, test, or entry point is named. Start by reproducing the corrupted message and tracing why it is retried indefinitely; done requires identifying the corruption source and establishing poison-message handling for this case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- backend, distributed-systems
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100