Skip to content

Feature/mu ed error handling#19

Open
m-messer wants to merge 4 commits into
mainfrom
feature/muEd-error-handling
Open

Feature/mu ed error handling#19
m-messer wants to merge 4 commits into
mainfrom
feature/muEd-error-handling

Conversation

@m-messer
Copy link
Copy Markdown
Member

Requires #17 and #18 to be merged to the main first.

This PR extends the previous implementation by adding the correct error handling.

@m-messer m-messer self-assigned this Apr 20, 2026
m-messer and others added 2 commits April 21, 2026 12:05
…on in handle_muEd_command

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
… or `200` codes, ensuring proper HTTP response for "UNAVAILABLE" status.
@m-messer m-messer force-pushed the feature/muEd-error-handling branch from 42f9184 to 40ab258 Compare April 21, 2026 11:07
@m-messer m-messer requested a review from neagualexa May 27, 2026 10:01
@m-messer m-messer assigned neagualexa and unassigned m-messer May 27, 2026
Comment thread handler.py
try:
version_error = check_muEd_version(event)
if version_error:
return wrap_muEd_response(version_error, event, 406)
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

are the response status codes somewhere as an enum? like do we need to define them or is there a library that sets the enums?

@neagualexa neagualexa assigned m-messer and unassigned neagualexa May 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants