Replies: 1 comment
-
|
yep, I'm using patched version from #1913 in prod :-) |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi folks, just wanted to start off by saying FastMCP is an amazing project. It's been a joy developing with it thus far.
That said, I am working on integrating FastMCP with an existing FastAPI service and I am having issues with the latest PyPI release when it comes with the
KVStorageusage and the OAuth flow. I am seeing no issues when using a single Granian worker, but when I ramp that up to more than 1 (which is what we'd need to use in production), OAuth flows fail if multiple calls along the OAuth flow hit different workers due to local state.I pulled in the latest FastMCP code as of yesterday, and adapted my Redis store interface to the new
AsyncKeyValueprotocol, and the issues seem to be fixed due to the updated OAuth storage interfacing added in #1913.Given this, I am wondering if there is an expected ETA for a new PyPI release that includes these changes (e.g. those in #1913)?
Thanks a ton!
Beta Was this translation helpful? Give feedback.
All reactions