Replace print() with structured logging in request/endpoint handlers#60
Merged
Merged
Conversation
request_handler.py and the http_server.py inference endpoint still used print() for server status/error output instead of the project's structured logger, so those messages bypassed log levels and handlers. Closes #12
This was referenced Jul 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
print()calls inrequest_handler.pyand thehttp_server.pyinference endpoint with the project's structuredlogger(info for status/registration messages, warning/error for failures).server/logger/log.py.Test plan
tests/unit/test_no_print_statements.py, a source-scan regression test asserting noprint(calls remain in these two files.uv run pytest tests/unit -m "not external_server and not model_artifact"passes (126 passed, 1 skipped).Closes #12