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.

Sign up for GitHub

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

Jump to bottom

JSON-RPC 0.8.0: structured traceback in CONTRACT_ERROR and TRANSACTION_EXECUTION_ERROR errors #2265

Closed
kkovaacs opened this issue Sep 25, 2024 · 0 comments · Fixed by #2317
Closed

JSON-RPC 0.8.0: structured traceback in CONTRACT_ERROR and TRANSACTION_EXECUTION_ERROR errors #2265

kkovaacs opened this issue Sep 25, 2024 · 0 comments · Fixed by #2317
Assignees
@kkovaacs
Milestone
JSON-RPC 0.8.0

Comments

@kkovaacs
Copy link
Contributor

kkovaacs commented Sep 25, 2024 •
edited
Loading

The new specification adds the (recursive) CONTRACT_EXECUTION_ERROR type for representing stack traces.

We don't currently have detailed stack trace information in the JSON-RPC code because the execution layer converts blockifier's blockifier::transaction::errors::TransactionExecutionError to a string right away. We should be returning a structured error instead and do the appropriate conversion to the JSON-RPC representation in the RPC code.

Reference: starkware-libs/starknet-specs@e8aad20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@kkovaacs kkovaacs

Labels
None yet
Projects
None yet
Milestone
JSON-RPC 0.8.0
Development

Successfully merging a pull request may close this issue.

feat(rpc/v08): add structured execution error call traces eqlabs/pathfinder
1 participant
@kkovaacs