fix bug with uvicorn and prometheus conflicting - #12
Merged
Conversation
…er with live reload now works
evanugarte
force-pushed
the
metrics-handler
branch
from
July 25, 2026 21:12
595745b to
253e35e
Compare
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.
Fix bug with uvicorn and prometheus conflicting, causing the program to crash.
When uvicorn starts the server, it imports server.py, rerunning all top-level code. This causes prometheus to create duplicate metrics and throw an error.
I created a metrics handler class to handle all prometheus metrics. This change is compatible with uvicorn's live reload