sneak/chat
1
0
Fork 0
Code Issues 7 Pull Requests Actions Packages Projects Releases Wiki Activity

http response codes should not be used in response to irc commands #54

New Issue
Closed
opened 2026-03-08 10:07:20 +01:00 by sneak · 1 comment
sneak commented 2026-03-08 10:07:20 +01:00
Owner
Copy Link

irc commands should be responded only with irc responses. http status codes should only be for session or client connection setup errors or internal server errors.

irc commands should be responded only with irc responses. http status codes should only be for session or client connection setup errors or internal server errors.
sneak added the bot label 2026-03-08 10:07:28 +01:00
clawbot was assigned by sneak 2026-03-08 10:07:32 +01:00
clawbot removed their assignment 2026-03-08 10:32:59 +01:00
clawbot commented 2026-03-08 10:33:18 +01:00
Collaborator
Copy Link

Implementation submitted in PR #56.

All IRC command handlers now respond with proper IRC numeric replies via the message queue instead of HTTP status codes. HTTP error codes are reserved for transport-level issues only (auth, malformed requests, server errors).

Numerics implemented: 001, 331, 332, 353, 366, 401, 403, 421, 432, 433, 442, 461 (plus existing 375, 372, 376).

docker build . passes (all tests, linting, formatting).

Implementation submitted in [PR #56](https://git.eeqj.de/sneak/chat/pulls/56). All IRC command handlers now respond with proper IRC numeric replies via the message queue instead of HTTP status codes. HTTP error codes are reserved for transport-level issues only (auth, malformed requests, server errors). **Numerics implemented:** 001, 331, 332, 353, 366, 401, 403, 421, 432, 433, 442, 461 (plus existing 375, 372, 376). `docker build .` passes (all tests, linting, formatting). <!-- session: agent:sdlc-manager:subagent:4ce97968-6fd5-47e4-9a6c-c96f5876ac3b -->
sneak closed this issue 2026-03-09 22:21:32 +01:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bot
Agent's turn to work
 merge-ready
All checks pass, reviewed, rebased, ready for merge
 needs-checks
make check does not pass cleanly
 needs-rebase
PR has merge conflicts or is behind main
 needs-review
Code review not yet done
 needs-rework
Code review found issues to fix
No Label bot
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
clawbot sneak
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sneak/chat#54
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?