Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: opentelemetry-php/exporter-zipkin
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: 1.2.0
Choose a base ref
...
head repository: opentelemetry-php/exporter-zipkin
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: 1.3.0
Choose a head ref
  • 1 commit
  • 1 file changed
  • 1 contributor

Commits on Jul 14, 2026

  1. fix(zipkin): store remote endpoint IPs as text, not raw binary/int (#… 

    …1998)

* fix(zipkin): store remote endpoint IPs as text, not raw binary/int

Zipkin's V2 JSON API expects ipv4/ipv6 on Endpoint as textual strings.
Storing raw inet_pton() bytes for IPv6 produced invalid UTF-8, crashing
json_encode(..., JSON_THROW_ON_ERROR) and dropping the whole span batch
for any CLIENT/PRODUCER span with a net.peer.ip IPv6 address. ipv4 had
the same class of bug, encoding as an integer instead of a dotted string.

* fix static analysis

* fix(zipkin): handle inet_pton() and inet_ntop() false returns

Both inet_pton() and inet_ntop() can return false. Check inet_pton()
result before passing to inet_ntop(), and check inet_ntop() result
before assigning to remoteEndpoint['ipv6']. Fall back to the original
IP string if either conversion fails.
    @jorgsowa
    jorgsowa authored Jul 14, 2026
    Configuration menu
    Copy the full SHA
    aaac0f4 View commit details
    Browse the repository at this point in the history
Loading