Better error codes and message when sebak has problems
Open
API
Proposal
- Dominant language
- Go
- Stars
- 44
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Description
When sebak has some problems like the consensus is failed or doesn't work, it should return HTTP 500 status code and properly message.
For example, when sebak can not make consensus and can not make new block, it still return 400 error to client like sebak is ok.
I also think it is hard to detect consensus problems but it is helpful for clients to show error messages properly.
Contributor guide
Assessment
This issue has not been assessed yet.