AFLplusplus/LibAFL

Replace .unwrap/.expect with meaningful errors

Open

#1,908 opened on Mar 4, 2024

View on GitHubContributor guide
 (11 comments) (0 reactions) (0 assignees)Rust (479 forks)github user discovery
good first issue

Repository metrics

Stars
 (2,621 stars)
PR merge metrics
 (Avg merge 17d 22h) (10 merged PRs in 30d)

Description

We use .unwrap/.expect in several places throughout the codebase. This should be changed to meaningful libafl::Error messages so that users know how to fix this, in case it is encountered.

Contributor guide

Research direction
Search the codebase for instances of .unwrap() and .expect() calls. For each occurrence, understand the context and replace with appropriate error handling using libafl::Error or other meaningful error types. Ensure error messages provide actionable guidance for users.
Tech stack
rust
Domain
securitytestingbackend
Issue type
Refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
RustError handling basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65