feat(portkey): Support instrumentation of portkey_ai.AsyncPortkey

[shotarok]

Add support for instrumentation of portkey_ai.AsyncPortkey

---

Note

Adds async instrumentation for portkey_ai.AsyncPortkey by wrapping AsyncCompletions.create, plus tests and cassettes.

• Instrumentation (Portkey):
  • Wrap AsyncCompletions.create in portkey_ai.api_resources.apis.{chat_complete,generation} with _AsyncCompletionsWrapper and track original for uninstrumentation.
  • Add _AsyncCompletionsWrapper to handle async spans, request/response attribute extraction, and span name AsyncCompletions.
  • Extend instrumentor slots to include _original_async_completions_create.
• Tests:
  • Add async tests test_async_chat_completion and test_async_prompt_template asserting span name/attributes.
  • Add corresponding VCR cassettes tests/cassettes/test_async_chat_completion.yaml and test_async_prompt_template.yaml.

^{Written by Cursor Bugbot for commit fac30e1. This will update automatically on new commits. Configure here.}

[github-actions]

CLA Assistant Lite bot All contributors have signed the CLA ✍️ ✅

[shotarok]

I have read the CLA Document and I hereby sign the CLA

[cursor]

Bug: Incomplete uninstrumentation leaves generation wrap active

The _uninstrument method does not properly restore AsyncCompletions.create from the generation module. During instrumentation (lines 64-68), AsyncCompletions.create is wrapped in both portkey_ai.api_resources.apis.chat_complete and portkey_ai.api_resources.apis.generation modules. However, the uninstrument method only imports and restores from the chat_complete module (lines 71-76), leaving the generation module's AsyncCompletions.create method wrapped even after uninstrumentation. This will cause the instrumentation to remain active for async completions called through the generation module even after calling uninstrument().

 

[shotarok]

If this is true, we would need to restore the sync function, in addition to the async function.