Ujjwaljain16 commented on issue #38806:
URL: https://github.com/apache/superset/issues/38806#issuecomment-5939452881
@rusackas
i investigated this against current `master` (`8ab7a85a3d`) and also ran a
6.1.0rc1 control environment
i could **not reproduce the reported `No application found` error** in
either environment on current master, `superset mcp run` works end-to-end with
JWT authentication in both stateless and stateful modes, including
`initialize`, `tools/list`, and DB-backed tools.
a few details from tracing the current implementation:
the `"Failed to validate request"` message comes from the MCP SDK's generic
request-processing exception handler; it does not identify the underlying
failure
the `"No application found..."` message is the Flask-SQLAlchemy 2.x error,
so the original failure appears to have involved Flask/SQLAlchemy access
without an application context somewhere in the request path
`#39385` changes app-context handling for the case where a context is
already present, to prevent concurrent tool calls from sharing `g`/`g.user`.
the no-context tool-call path already pushed an app context in 6.1.0rc1
`#38747` changes JWT-to-user resolution and stale `g.user` handling; it
does not introduce the missing app-context behavior.
i therefore don't think we can attribute the original issue to either #38747
or #39385, and i don't see a current production-code change justified by the
reproduction so far
there are still differences from the original report: my reproduction used
HS256 rather than RS256/JWKS
the exact exception that originally escaped into the MCP SDK's `"Failed to
validate request"` handler therefore remains unidentified
if this is still reproducible on a current 6.1.x/master deployment, a full
server-side traceback around the `"Failed to validate request"` message would
be especially useful to identify the failing layer
otherwise, it would be useful for the original reporters to retest on 6.1.0
or current master
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
