Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

nearcore doesn't always return structured errors #2572

Closed
vgrichina opened this issue Apr 29, 2020 · 2 comments
Closed

nearcore doesn't always return structured errors #2572

vgrichina opened this issue Apr 29, 2020 · 2 comments
Assignees

Comments

@vgrichina
Copy link
Collaborator

Describe the bug

When submitting transaction nearcore at least sometimes returns structured errors (usually unfortunately just Timeout). When making a contract method view call – non-structured errors are returned. This may apply to other calls as well – investigation is needed on which RPC calls are affected.

To Reproduce
Make a view call on any contract that results in error.

Expected behavior
Structured error is returned.

@vgrichina
Copy link
Collaborator Author

[I] ➜ http post https://rpc.betanet.nearprotocol.com jsonrpc=2.0 method=tx params:='["CqiBnYCRgkGV2odJPXJTBkoZHXjDNQFJKw7oRYWU1j6g", "betanet"]' id=dontcare
HTTP/1.1 200 OK
Connection: keep-alive
Content-Length: 162
Content-Type: application/json
Date: Mon, 27 Apr 2020 23:14:13 GMT
Server: nginx/1.14.0 (Ubuntu)

{
    "error": {
        "code": -32000,
        "data": "Transaction CqiBnYCRgkGV2odJPXJTBkoZHXjDNQFJKw7oRYWU1j6g doesn't exist",
        "message": "Server error"
    },
    "id": "dontcare",
    "jsonrpc": "2.0"
}

@bowenwang1996
Copy link
Collaborator

duplicate of #2536

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants