[Bug]: Metadata, Cache, and trace_id fields are not registered about portkey-python-sdk

[dosubot]

🤖

Hello Ahmed,

Thank you for reaching out and providing a detailed description of the issue you're facing.

Based on the current version of Portkey Python SDK (v0.1.53), the cache, trace_id, and metadata fields are indeed supported and should be respected when included in the request. This is confirmed by the Constructs class in the SDK's source code.

However, from the information you've provided, it seems like these fields are not being registered as expected. This is not a known issue with the current version of the SDK, and I couldn't find any related issues or pull requests in the repository that could explain this behavior.

To help us investigate this further, could you please provide the following additional information:

1. Are there any error messages being returned when you make the request?
2. Could you confirm if the issue persists across different environments or is it specific to a particular setup?
3. Have you tried using different values for the cache, trace_id, and metadata fields to see if the issue persists?

Your cooperation is greatly appreciated and will help us resolve this issue more effectively.

Best regards,
Dosu

Sources

• portkey/api_resources/utils.py

---

This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research.

Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant.

If you want to continue the conversation, start your reply with @dosu-bot.

[noble-varghese]

@Rashwan This is indeed a bug and is a known issue on our side. We're working on it and will be fixed ASAP.

[Rashwan]

Thank you @noble-varghese for the quick response, please let me know when it is fixed 🙏

[noble-varghese]

@Rashwan The problem with the trace-id and metadata capture has been successfully addressed, and we have included a screenshot for your reference. While we have not yet resolved the cache issue at this moment, please be assured that it will be fixed by the end of this week as we are currently implementing significant updates to the SDKs and related services. We appreciate your patience and thank you for reporting the issue. Rest assured, we are committed to resolving any future issues more swiftly.