fix: Mcp tutorial instrumentation and server file path #7635
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dosubot
bot
added
the
size:M
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The current tutorial was not reproducible for due to incorrect server path and more notably the instrumentation flow. The instrumentation flow depends on the instrumentation hooks to be registered before the corresponding modules are imported.
(Also made the instrumentation more explicit, instead of
auto_instrument, which is more reproducible)Because of the unconventional import flow this depends on #7634 to pass CI checks
To ensure context propagation works as intended I have also PRed this fix to the existing MCP instrumentation Arize-ai/openinference#1644