Skip to content

Backend error-code and error-response catalog #555

Closed

Description

@codebestia

Write apps/backend/docs/contracts-error-catalog.md: every error shape the backend returns, across both transports. REST handlers return { error, ... } with varying extra fields; socket handlers emit an error event whose payload carries an event name and sometimes a code. There is currently no single place to look up what a client can receive.

Acceptance criteria:

  • One table of REST errors: status, error string, extra fields, and the route(s) that emit it
  • One table of socket errors keyed by the emitted event value, including the non-obvious ones — device_set_mismatch, protocol_mismatch, rate_limited, envelope_too_large
  • Documents which errors are retryable and which are terminal
  • Notes the rate-limit response shape (429 plus Retry-After and RateLimit-* headers)

Activity

  1. cynthia1-rgb commented on Aug 27, 2026

    @cynthia1-rgb

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

    Hi, I have relevant experience with the underlying technology here and would like to take this issue.

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

  2. Deb-Auth commented on Aug 30, 2026

    @Deb-Auth

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

    I'm interested in working on this issue. I'll carefully follow the project's guidelines and submit a tested, maintainable solution.

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

  3. drips-wave commented on Aug 30, 2026

    @drips-wave

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

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

  4. added a commit that references this issue on Aug 31, 2026
    ed612f1
  5. github-actions commented on Aug 31, 2026

    @github-actions

    Closed by #597, merged into dev.

  6. drips-wave commented on Aug 31, 2026

    @drips-wave

    This issue has been completed by @Deb-Auth as part of the Stellar Wave Program's 8th Wave 🥳

    😎 @Deb-Auth: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

    🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Stellar WaveIssues in the Stellar wave programbackenddocumentationImprovements or additions to documentation

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions