Add contract test: bump_stream() on a nonexistent stream ID returns StreamNotFound

[Austinaminu2]

Description

Every other read/write contract function has a negative-path test for a nonexistent stream ID, but `bump_stream()` does not.

Task

Add a test calling `bump_stream()` with an invalid/nonexistent stream ID and asserting it returns `StreamError::StreamNotFound`, matching the pattern used for the equivalent tests on other functions.

Good for contributors because

Small, mechanical test addition following an existing, well-established pattern in the test suite.

[Michael997glitch]

@Michael997glitch has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

I’ve resolved similar problems in the past and am confident I can implement a clean, efficient fix quickly,if am given the opportunity.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Michael997glitch to this issue.

[soma-enyi]

@soma-enyi has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi team, I'd like to work on this issue. I'm a full-stack developer experienced in TypeScript, Rust, and smart contract development across EVM and Soroban/Stellar ecosystems. I've built and shipped production systems covering backend APIs, frontend interfaces (Next.js, React), CI/CD pipelines, and onchain protocols — so I'm comfortable working across whatever layer this issue touches. My approach I'll start by reproducing the issue locally and reading the surrounding code to understand context and constraints. I'll scope the fix tightly to avoid unnecessary churn, write or update tests to cover the change, and make sure linting, formatting, and existing CI checks all pass before opening a PR. If anything in the issue is ambiguous, I'll flag it early rather than guess. What you can expect A single clean PR with a clear description linking back to this issue. Minimal, well-tested changes that follow the project's existing conventions. Fast turnaround — I'm available to start immediately and responsive to review feedback. Happy to discuss the approach further if needed. Looking forward to contributing.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @soma-enyi to this issue.

[escaprt]

@escaprt has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

I’d like to work on Issue #658 because bump_stream() should return a clear StreamNotFound error when called with a stream ID that does not exist. Adding a dedicated regression test will make this expected behavior explicit and protect it from future changes.

I will first review the bump_stream() implementation, the StreamError definitions, and the existing contract test patterns to see how nonexistent stream cases are currently handled.

I will then add a focused contract test that calls bump_stream() with an invalid or nonexistent stream ID and verifies that the transaction fails with the expected StreamNotFound error rather than producing an unrelated failure or panic.

I will keep the test isolated and deterministic, using the existing contract test setup and fixtures without introducing new dependencies or modifying unrelated stream behavior.

I will also check whether the current implementation already returns the correct typed error. If it does, the change will remain limited to regression coverage; if the test exposes a mismatch, I will make the smallest necessary adjustment to align the implementation with the documented contract.

Finally, I will run the relevant contract tests and build checks to confirm the new regression test passes consistently.

My goal is to clearly guarantee that attempting to bump a nonexistent stream fails with StreamNotFound, giving callers a predictable error and protecting this behavior from future regressions.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @escaprt to this issue.

[drips-wave]

Congratulations, @soma-enyi! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

🧑‍💻 @soma-enyi: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊