Exceptions handling and structure
Open
Nobody has claimed this yet.
help wanted
Interoperability
- Dominant language
- Python
- Stars
- 624
- Forks
- 256
- Avg merge
- 1d 34m
- Merged PRs (30d)
- 47
Description
- We should revisit the whole codebase to ensure exceptions are well defined and handled well.
- We don't have a good picture of the exception tree now. As a reference, in trinity, the package
trinityhas its own exception tree and so dop2p. I'm not sure what is the best structure for us, but I think probably a single exception tree(i.e. all exceptions inherit fromBaseLibp2pErrorand its descendants) can be a start?
@ChihChengLiang @ralexstokes @NIC619 @pipermerriam
Would love to have your comment on it:)
Contributor guide
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 reviewing libp2p/exceptions.py and the linked Trinity and p2p exception trees. Then inventory exception definitions and handling across the codebase, and seek agreement on a hierarchy and handling policy. Done means the structure and scope are decided and the affected exceptions are consistently organized.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100