Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Test that failed Whale multi-input lowering preserves all outputs

Open Beginner friendly
  • Is something wrong?
#894 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
78/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
rust
Domain
cli, testing

Research direction

Start with the multi-input lowering flow in src/cli.rs and the existing output-preservation tests in tests/whale_backend.rs. Add CLI coverage for failed second-source lowering, a successful pair, and colliding output plans; run the Whale backend tests. Done when all three cases verify the specified output preservation or failure behavior.

Written by the indexing model from the issue text.

Description

enhancement good first issue needs testing

Motivation

src/cli.rs lowers all inputs before publishing output, but tests/whale_backend.rs only exercises previous-output preservation for a single source. The cross-input guarantee has no focused regression.

Scope

Add a CLI test with two Wave inputs and preexisting .wir outputs. Let the first lower successfully and the second fail; verify neither output changes. Also cover a successful pair and colliding output plans. Do not redesign multi-file filesystem transaction semantics.

Difficulty: easy.

Completion criteria

  • Assert failed second-source lowering leaves both previous outputs intact.
  • Assert a successful pair emits separate verified files.
  • Check output-plan collisions fail before replacing files.
Dominant language
Rust
Stars
56
Forks
21
Avg merge
4h 58m
Merged PRs (30d)
54

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from wavefnd/Wave

All issues in wavefnd/Wave

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.