You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just this day discovered a bug when using a2wsgi v1.8.0 along with FastAPI v0.110.0 (after having upgraded from v0.104.1). After some investigation, it turned out that the issue was resolved by bumpung a2wsgi to the most recent release, but I am curious what the issue was. Do you maintain any kind of release notes that could explain why there used to be a bug, and how it was resolved?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I just this day discovered a bug when using a2wsgi v1.8.0 along with FastAPI v0.110.0 (after having upgraded from v0.104.1). After some investigation, it turned out that the issue was resolved by bumpung a2wsgi to the most recent release, but I am curious what the issue was. Do you maintain any kind of release notes that could explain why there used to be a bug, and how it was resolved?
Beta Was this translation helpful? Give feedback.
All reactions