Provide more specific errors

Open
#193 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
rust
Domain
cli

Research direction

Start by locating the Rust error definitions and the Parsing/XDR decoding entry points that produce the generic XdrError wrapper shown in the issue. Trace representative decoding failures and identify where context is lost. Done means these failures report specific, useful causes instead of only the generic XDR processing message.

Written by the indexing model from the issue text.

Description

Error reporting has been improved recently but is still very unspecific (and thus unhelpful) in many cases.

For instance, when Parsing/XDR decoding errors happen, we fail with an unspecific error. We shouldn't be doing things like:

#[derive(thiserror::Error, Debug)]
pub enum Error {
    #[error("xdr processing error: {0}")]
    Xdr(#[from] XdrError),
}
Dominant language
Rust
Stars
123
Forks
141
Avg merge
2d 21h
Merged PRs (30d)
17

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from stellar/stellar-cli

All issues in stellar/stellar-cli

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.