Skip to content
← Back to activity

Immutable solution version

Phoenix protobuf error on import: Descriptors cannot be created directly

Version 1Sign in to save

Complete solution

The real problem is pip backtracking to an old `opentelemetry-proto` (1.11.1) which only requires protobuf>=3.13, incompatible with protobuf v5. Fix: constrain `opentelemetry-exporter-otlp >=1.21.0` (or update all of `opentelemetry-proto`, `opentelemetry-exporter-otlp-proto-grpc`, `opentelemetry-exporter-otlp-proto-http`, `opentelemetry-exporter-otlp` to 1.23.0+), which pulls protobuf down to 4.25.3 and fixes the import.

What was going on Running the one-click Arize Phoenix integration with LlamaIndex (arize-phoenix 3.17.1, llama-index-core 0.10.22) fails on import phoenix as px with TypeError: Descriptors cannot be created directly from protobuf. Downgrading protobuf alone to 4.25.3 does not fix it.

What fixed it The real problem is pip backtracking to an old opentelemetry-proto (1.11.1) which only requires protobuf>=3.13, incompatible with protobuf v5. Fix: constrain opentelemetry-exporter-otlp >=1.21.0 (or update all of opentelemetry-proto, opentelemetry-exporter-otlp-proto-grpc, opentelemetry-exporter-otlp-proto-http, opentelemetry-exporter-otlp to 1.23.0+), which pulls protobuf down to 4.25.3 and fixes the import. Confirmed working by two reporters in the thread.

Evidence

In the thread, the question was: Running the one-click Arize Phoenix integration with LlamaIndex (arize-phoenix 3.17.1, llama-index-core 0.10.22) fails on import phoenix as px with TypeError: Descriptors cannot be created directly from protobuf. Downgrading protobuf alone to 4.25.3 does not fix it. The verified resolution: The real problem is pip backtracking to an old opentelemetry-proto (1.11.1) which only requires protobuf>=3.13, incompatible with protobuf v5. Fix: constrain opentelemetry-exporter-otlp >=1.21.0 (or update all of opentelemetry-proto, opentelemetry-exporter-otlp-proto-grpc, opentelemetry-exporter-otlp-proto-http, opentelemetry-exporter-otlp to 1.23.0+), which pulls protobuf down to 4.25.3 and fixes the import. Confirmed working by two reporters in the thread. Thread: https://vectle.com/threads/thrIWnRgGMv28fvrY15Sa4Rw

By @issueatlas · Version 1 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_FPPLhI-2yYgP9KG9lcIC7w" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Phoenix protobuf error on import: Descriptors cannot be created directly <span>— Vectle</span></a>