[Backend] Negative offset/page returns 500 (Prisma) instead of 400 on list endpoints

[grantfox-oss]

Telegram (ask questions / claim the issue here first): https://t.me/+DOylgFv1jyJlNzM0

Why this matters

stream.controller.ts:181 (Number.parseInt(offset,10) || 0) and :297-298, plus user.controller.ts:88, keep a negative parsed value (-5 is truthy, so || 0 does not replace it) and pass it straight to Prisma skip. Prisma rejects a negative skip with a validation error, returned as 500. So GET /v1/streams?offset=-1 and the events endpoints all 500. The correct guard already exists in events.routes.ts:96.

Acceptance criteria

• Negative offset/page on the listing endpoints returns 400 or is clamped to 0
• Apply the same >= 0 clamp used in events.routes.ts:96 to listStreams, getStreamEvents and getUserEvents
• Add a test asserting a negative offset no longer yields 500

Files to touch

• backend/src/controllers/stream.controller.ts
• backend/src/controllers/user.controller.ts

Out of scope

• Cursor-based pagination changes

[GiftedGiftB]

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

I can get this work done in less than 30 minutes.

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

[Ssoleed]

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

hi maintainer, pls can i work on this issue please

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

[NEA-DEV-coder]

@NEA-DEV-coder has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

I’d like to work on this issue.

I plan to update the affected listing endpoints to consistently validate pagination parameters by applying the same non-negative offset/page guard already used in events.routes.ts. This will prevent negative values from reaching Prisma, ensuring requests return a 400 response (or are safely clamped to 0) instead of a 500 error. I’ll implement the fix in stream.controller.ts and user.controller.ts, then add regression tests confirming negative offsets no longer trigger Prisma validation errors while preserving existing pagination behavior.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @NEA-DEV-coder to this issue.

[Godbrand0]

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

hello, i would like to work on this issue

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

[drips-wave]

Congratulations, @Godbrand0! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @Godbrand0: 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 🌊

[grantfox-oss]

🦊 GrantFox — @Godbrand0 has been assigned to this issue!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #811)
2. Your PR will be reviewed by the LabsCrypt maintainers

Good luck! Track your progress on GrantFox.

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox!

@Godbrand0's PR #943 was approved and merged by @ogazboiz.

🏆 @Godbrand0: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (293 total points). Track your full progress on GrantFox.

👏 Great work, @Godbrand0! Keep contributing to LabsCrypt.