FuelLabs/fuel-core

Avoid usage of the `BoxedStream` from the ports in services

Open

#2,836 opened on Mar 10, 2025

View on GitHub
 (4 comments) (0 reactions) (0 assignees)Rust (57,084 stars) (2,861 forks)batch import
good first issuetech-debt

Description

We have many places in the codebase where we require the port to return a BoxedStream, while instead, it could have a generic trait with async method

Source: https://github.com/FuelLabs/fuel-core/pull/2791#discussion_r1985721863

Contributor guide

Tech stack
rust
Domain
backend
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.
3-5 days
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
Rustasync/awaitgeneric traitsFuel core architecture
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Review the codebase for uses of BoxedStream in port definitions. Examine the referenced PR #2791 discussion for context. Identify patterns where BoxedStream can be replaced with a generic trait with async method. Ensure changes are consistent across services.
Avoid usage of the `BoxedStream` from the ports in services · FuelLabs/fuel-core#2836 | Good First Issue