-
Notifications
You must be signed in to change notification settings - Fork 84
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Test test_expose_defaults
fails due to NameError
after updating
#219
Comments
test_expose_defaults
fails due to NameError
after updating fastapi
and starlette
test_expose_defaults
fails due to NameError
after updating
Hey @tiangolo, any idea what might have changed with the update that results in the test suddenly failing? The hotfix seems to work (see PR) but would still be interesting to know |
Hey there 👋 Came across this and I thought I would put my two cents in. I think this problem was introduced because since Starlette 0.24.0, the middleware stack is built only once when app starts (and not each time IMHO, the fact that |
This latest PR 220 fixed the issue in our environment. Looking forward to the PyPI update. Was seeing it on an older version of starlette though:
|
Pull request #153 introduced new parameter
registry
to set Prometheus client registry. It also added two tests to cover this enhancement.After running
poetry update
on commit 8cec83b thetest_expose_defaults
started to fail.Before that it worked fine. It tried to debug it. The Prometheus client lib is complaining about duplicate metrics as excepted.
Problems start when updating starlette and fastapi
The text was updated successfully, but these errors were encountered: