[new release] opentelemetry (9 packages) (0.90)

[c-cube]

Core library for instrumentation and serialization for https://opentelemetry.io

• Project page: https://github.com/ocaml-tracing/ocaml-opentelemetry

CHANGES:

• major refactor: split library into opentelemetry.core, opentelemetry,
  opentelemetry.util, opentelemetry.emitter, opentelemetry.atomic, revamp internals
• per-signal providers: separate trace, meter, and logger providers replace
  the single monolithic exporter
• opentelemetry.ambient-context is now a standalone library, once again
• new opentelemetry-client-ocurl-lwt package
• client: split opentelemetry-client-sync off of the main client library
• client: add support for http/json protocol alongside http/protobuf
• client: add HTTP retry with exponential backoff
• client: overhaul bounded queue; introduce generic consumer framework
• client: add Exporter_add_batching, Emitter_add_batching, Emitter_sample,
  Emitter_limit_interval combinators. Batching is factored out of individual
  client libraries.
• client: add sampler as an emitter transformer
• client: add exporter_stdout and debug_exporter
• client: add self_metrics and self_debug to exporters
• client: add after_shutdown callback in ocurl/ocurl-lwt clients
• Span.dummy: inert span that is never modified
• Span.record_exception now also sets the span status to error
• Span.set_span_status added in opentelemetry.trace
• Span: carry flags to span_link
• Span: now mutable thanks to ocaml-protoc 4.0, replaces old Scope.t entirely
• Meter.emit and Meter_provider.emit_l added
• emitter: add flat_map, tap, to_list, enabled combinators
• clock abstraction added; ptime used by default in logger and metrics
• interval limiter used for metrics_callbacks
• update to OTEL spec 1.8.0
• update semantic conventions
• various bug fixes and performance improvements

[jmid]

Thanks!

It looks like the mtime bounds needs adjusting:

• opentelemetry-client-cohttp-lwt.0.90 lower-bounds (failed: Unbound value Mtime.Span.is_shorter)
• opentelemetry-cohttp-lwt.0.90 lower-bounds (failed: Unbound value Mtime.Span.is_shorter)
• opentelemetry-lwt.0.90 lower-bounds (failed: Unbound value Mtime.Span.is_shorter)

and that some *lwt dependencies are a bit off:

• opentelemetry-client-ocurl-lwt.0.90 (failed: Library "opentelemetry-client.lwt" not found.)
• opentelemetry.0.90 (failed: Package "lwt" doesn't exist in the current project and isn't installed)

[mseri]

Can you look at these failures?

opentelemetry-client-cohttp-eio.0.90 tests (failed: Library "opentelemetry-lwt" not found.)

opentelemetry-client-ocurl.0.90 tests (failed: Failed to get sources of curl.0.10.0, curl_lwt.0.10.0, ocurl.transition (https://github.com/ygrek/ocurl/releases/download/0.10.0/curl-0.10.0.tbz): curl failed)

opentelemetry.0.90 tests (failed: Library "opentelemetry-client" not found.)

[mseri]

I think tests should be disabled on macos since network is not available in the ci sandbox

[c-cube]

A bit mystified by the download errors for curl 🤷 . I'm not going to disable macOS tests just because of opam-ci, so I think it's overall good?

[c-cube]

it looks like curl exits with code 6, which is host resolution error (https://curl.se/libcurl/c/libcurl-errors.html and https://everything.curl.dev/cmdline/exitcode.html). So the CI box cannot resolve github.com (?!)

[mseri]

The issue you see is an intermittent rate-limitation the CI incurs every now and then

[mseri]

Thanks