Open Issues Need Help
View All on GitHub Library should not log fatal errors about 3 hours ago
AI Summary: The library's current practice of logging fatal errors causes the client application to crash, preventing graceful error handling. This can lead to a CrashLoopBackOff scenario where an invalid message repeatedly triggers a panic upon restart after recovery attempts. The issue suggests the library should instead return errors or log them non-fatally, enabling the client to handle errors gracefully.
Complexity:
4/5
enhancement good first issue
A go client that adds kafka like semantics for failure handling to redis streams
Go