vectordotdev/vector

Investigate and eliminate `allow` statements

Open

#23659 opened on Aug 27, 2025

View on GitHub
 (5 comments) (0 reactions) (0 assignees)Rust (21,837 stars) (2,126 forks)batch import
good first issuehacktoberfesthave: nicetype: tech debt

Description

Module wide: https://github.com/search?q=repo%3Avectordotdev%2Fvector%20%22%23!%5Ballow(%22&type=code

These allows can hide bugs: https://github.com/search?q=repo%3Avectordotdev%2Fvector+clippy%3A%3Acast&type=code

Obviously this can be in multiple independent PRs.

Contributor guide

Tech stack
rust
Domain
backendobservability
Issue type
refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
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.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
RustClippy
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50
Research direction
Examine each occurrence of `#[allow(...)]` in the codebase, focusing on Clippy specific allows. For each, determine whether the suppressed lint can be addressed by improving the code (e.g., using proper types, rewriting logic) and remove the allow if possible. If the allow is necessary, document why. Work in independent PRs per module. Refer to the linked search results for a list of allow statements.