fix: avoid cluttering logs with simple message queue polling #429
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.
Fixes #428
After the refactoring, the SimpleMessageQueue behaves like a pubsub system with the client polling for messages, similar to Redis for example. Using plain HTTP calls as the pubsub protocol, the client keeps
GET
ting the endpoint on the server to get messages (if any) for the whole application lifetime, and uvicorn happily fills the access logs with noise.This PR filters out polling requests to the
/messages
endpoint from the access logs.