Open ar-or opened 1 hour ago
Hello @ar-or 👋 I'm here to help you with any bugs, questions, or contribution inquiries you may have.
The error you're encountering seems to be related to two main issues in the agenta-backend
:
UUID Parsing Error: The error message ValueError: badly formed hexadecimal UUID string
indicates that the parse_ingest_value
function is trying to convert a string to a UUID, but the string is not in the correct format. This suggests that the data being sent might contain an invalid UUID string. You should verify that all UUIDs in your trace data are correctly formatted before they are sent to the backend.
Dictionary Size Change During Iteration: The RuntimeError: dictionary changed size during iteration
suggests that the code is attempting to modify a dictionary while iterating over it. This can happen if the dictionary is being altered (e.g., adding or removing keys) during the iteration process. To resolve this, ensure that any modifications to the dictionary are done outside of the iteration loop. You might need to create a copy of the dictionary keys before iterating over them to avoid this error.
To address these issues, you should:
parse_ingest
function to ensure that the dictionary is not being modified during iteration. Consider iterating over a list of keys instead of the dictionary directly to prevent this error.These steps should help in resolving the 500 Internal Server Error you're experiencing with the OTLP traces.
To continue talking to Dosu, mention @dosu.
Describe the bug When a python script provisioned with ag.init() tries to send traces, the agenta backend responds with 500
To Reproduce
Expected behavior Expected no error
Network Logs via tcp dump between containers: