tarantool / tarantool/migrations
More clear error messages in http responses
Nobody has claimed this yet.
- Dominant language
- Lua
- Stars
- 20
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
Currently, /up http handler provides unclear error messages when something goes sour (basically, 500 with "something went wrong text").
It would be nice to have detailed error report (which migration failed on which instance, and which actually applied) available both in logs AND http response body
Contributor guide
No contributing guide indexed for this repository
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 at the /up HTTP handler and trace how migration failures currently become the generic 500 response. Determine how to report which migration failed, on which instance, and which migrations applied in both logs and the response body. Done means those details replace the generic error for migration failures.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100