fix(web): enable reqwest stream feature for bunyip-web #88

Merged

longjacksonle merged 1 commit from fix/bunyip-web-reqwest-stream into main

2026-06-10 01:23:04 +02:00

longjacksonle commented

2026-06-10 01:03:31 +02:00

Owner

What

Add the stream feature to bunyip-web's reqwest dependency.

Why

bunyip-web's download proxy (bunyip-web/src/handlers/dashboard.rs) calls resp.bytes_stream() / Body::from_stream(...), which require reqwest's stream feature. The crate declares reqwest with default-features = false and did not list stream, so a targeted build fails:

error[E0599]: no method named `bytes_stream` found for struct `reqwest::Response`

A full workspace build hides this: another member (bunyip-oci) enables reqwest stream, and Cargo feature unification turns it on for the shared reqwest build - so CI / cargo build --workspace pass. But the dev container runs cargo watch -x 'run -p bunyip-web', whose narrower graph does not get that unification, so the login UI fails to rebuild and Traefik returns 502. (Hit live: the dev login page went 502 after a rebuild.)

Fix

List stream in bunyip-web's own reqwest features so it builds standalone, independent of feature unification.

Verification

cargo check -p bunyip-web now compiles (it errored before), and the dev web container came back up (Web listening on http://0.0.0.0:4400); the login path serves 200 again.

🤖 Generated with Claude Code

## What Add the `stream` feature to `bunyip-web`'s `reqwest` dependency. ## Why `bunyip-web`'s download proxy (`bunyip-web/src/handlers/dashboard.rs`) calls `resp.bytes_stream()` / `Body::from_stream(...)`, which require reqwest's `stream` feature. The crate declares reqwest with `default-features = false` and did not list `stream`, so a **targeted** build fails: ``` error[E0599]: no method named `bytes_stream` found for struct `reqwest::Response` ``` A full workspace build hides this: another member (`bunyip-oci`) enables reqwest `stream`, and Cargo feature unification turns it on for the shared reqwest build - so CI / `cargo build --workspace` pass. But the dev container runs `cargo watch -x 'run -p bunyip-web'`, whose narrower graph does not get that unification, so the **login UI fails to rebuild and Traefik returns 502**. (Hit live: the dev login page went 502 after a rebuild.) ## Fix List `stream` in `bunyip-web`'s own reqwest features so it builds standalone, independent of feature unification. ## Verification `cargo check -p bunyip-web` now compiles (it errored before), and the dev web container came back up (`Web listening on http://0.0.0.0:4400`); the login path serves 200 again. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

longjacksonle added 1 commit

2026-06-10 01:03:31 +02:00

fix(web): enable reqwest "stream" feature for bunyip-web

Check / fmt / clippy / build / test (pull_request) Successful in 1m6s

Details

Create release / Create release from merged PR (pull_request) Has been skipped

Details

2a71b2ab87

bunyip-web's download proxy (dashboard.rs) calls resp.bytes_stream() and Body::from_stream(...), which require reqwest's "stream" feature. bunyip-web declares reqwest with default-features = false and did not list "stream", so a targeted `cargo run -p bunyip-web` (what the dev container runs via cargo watch) fails to compile:

  error[E0599]: no method named `bytes_stream` found for struct `reqwest::Response`

A full workspace build masks this: another member (bunyip-oci) enables reqwest "stream", and Cargo feature unification turns it on for the shared reqwest build, so CI and `cargo build --workspace` compile fine. The narrower `-p bunyip-web` graph does not get that unification, so the dev login UI fails to (re)build and serves 502.

Add "stream" to bunyip-web's own reqwest features so the crate builds standalone. Verified: `cargo check -p bunyip-web` compiles and the dev web container comes back up (listening on 4400).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>