Missing error details on API error
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 49
- Forks
- 31
- PR merge metrics
- No merged PRs in 30d
Description
The error created from an error response from API calls is missing and not printing extra information in the json.error.details object that would be useful for developers to see. Only the json.error.name and json.error.what is printed.
Error response from v1.chainpush_transaction:
{
headers: {
'access-control-allow-headers': '*',
'access-control-allow-origin': '*',
connection: 'close',
'content-length': '531',
'content-type': 'application/json',
server: 'WebSocket++/0.7.0'
},
status: 500,
json: {
code: 500,
message: 'Internal Service Error',
error: {
code: 3090003,
name: 'unsatisfied_authorization',
what: 'Provided keys, permissions, and delays do not satisfy declared authorizations',
details: [
{
message: "transaction declares authority '${auth}', but does not have signatures for it under a provided delay of 0 ms, provided permissions ${provided_permissions}, provided keys ${provided_keys}, and a delay max limit of 3888000000 ms",
file: 'authorization_manager.cpp',
line_number: 532,
method: 'check_authorization'
}
]
}
},
text: '{"code":500,"message":"Internal Service Error","error":{"code":3090003,"name":"unsatisfied_authorization","what":"Provided keys, permissions, and delays do not satisfy declared authorizations","details":[{"message":"transaction declares authority \'${auth}\', but does not have signatures for it under a provided delay of 0 ms, provided permissions ${provided_permissions}, provided keys ${provided_keys}, and a delay max limit of 3888000000 ms","file":"authorization_manager.cpp","line_number":532,"method":"check_authorization"}]}}'
}
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 by tracing how API errors from v1.chainpush_transaction are created and formatted in the TypeScript client. Reproduce the shown error response and inspect the handling of json.error.details; done means the useful detail information is included alongside the existing name and what output, with a regression test if the project has coverage for this path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, blockchain
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100