You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
TraceError and TraceResult are defined in the OpenTelemetry API crate (source) and are used internally within the API implementation. Since the API itself should not return error objects, it would be preferable to either remove them from the API or move them to the SDK if they are needed there. The same consideration applies to ExportError.
The text was updated successfully, but these errors were encountered:
lalitb
changed the title
[Trace API] Error cleanup - TraceError, TraceResult, ExportError
[Trace API] API should not expose errors: Consider removing TraceError, TraceResult, and ExportError
Feb 5, 2025
lalitb
changed the title
[Trace API] API should not expose errors: Consider removing TraceError, TraceResult, and ExportError
[Trace API] API should not expose errors: consider removing TraceError, TraceResult, and ExportError
Feb 5, 2025
lalitb
changed the title
[Trace API] API should not expose errors: consider removing TraceError, TraceResult, and ExportError
[Trace API] Cleanup: Remove TraceError, TraceResult, and ExportError
Feb 5, 2025
TraceError
andTraceResult
are defined in the OpenTelemetry API crate (source) and are used internally within the API implementation. Since the API itself should not return error objects, it would be preferable to either remove them from the API or move them to the SDK if they are needed there. The same consideration applies to ExportError.The text was updated successfully, but these errors were encountered: