Adrian Cole
Adrian Cole
PS I do think we all should be able to learn this stuff as we inherit this complexity also helping people trace things in brave for example. It isn't bad...
here is an example of hung requests. While this is probably a bug, it is the sort of thing that we should have some notes about in the "don't panic"...
very good start here https://github.com/line/armeria/pull/1938
@openzipkin/armeria I'm going to ask a question here because I think it is important to know. in #2760, we changed to do this as opposed to what we did before.....
Glad to see this open, as I missed it but thought exactly the same (I think) for some time, summarized [here](https://github.com/modelcontextprotocol/modelcontextprotocol/discussions/269#discussioncomment-12784319) Basically some means of using message fields to inject...
@smola cool are you thinking a dict like this that could be left out if anything decides to either not encode it or not parse it? or are you thinking...
@smola ps the way the OpenInference experiment ([python](https://github.com/Arize-ai/openinference/tree/main/python/instrumentation/openinference-instrumentation-mcp), [javascript](https://github.com/Arize-ai/openinference/tree/main/js/packages/openinference-instrumentation-mcp)) works is via an optional dependency (currently in openinference, but could be adopted by opentelemetry directly as well). https://github.com/elastic/observability-examples/blob/c8334260c42d5338a0e844d5752532f457e5d0fe/genai-function-calling/openai-agents/requirements.txt#L8 This means...
TL'DR' I think there's a tacit agreement and also uncoordinated independent usage of `request.params._meta`. Where's the best place to document this? Details below to follow or ignore --- I didn't...
I went ahead and raised a PR to document this. Please let me know if something should be worded differently or in another place https://github.com/modelcontextprotocol/modelcontextprotocol/pull/414