Execution Profile

garnet-labs/codex

Recorded at the kernel by Garnetfor commit b0ad6a5 (merge ref)

Garnet runtime coverage/python-sdk-install

run 33097033722

Execution chains

15 destinations · 2 processes
  • systemd
    • dockerd[1313 · dockerd]
      • registry-1.docker.io100.51.90.123:443 (https) · tcp
      • auth.docker.io104.18.43.178:443 (https) · tcpalso recorded: auth.docker.io.cdn.cloudflare.net
      • production.cloudfront.docker.com18.155.173.114:443 (https) · tcpalso recorded: d3ipk8a4rcghwr.cloudfront.net
      • d3ipk8a4rcghwr.cloudfront.net18.155.173.80:443 (https) · tcpalso recorded: production.cloudfront.docker.com
      • localhost127.0.0.53:53 (dns) · udp(dns resolver)
    • containerd-shim-runc-v2dash
      • uv[2601 · uv]
        • pypi.org151.101.0.223:443 (https) · tcp
Run details
Repositorygarnet-labs/codex
WorkflowGarnet runtime coverage
Jobpython-sdk-install
Run ID33097033722
Profile UUID01a04434-7eec-760c-be58-3a45b59bb789
Commit SHAb0ad6a5590f88bc1c02f1f945934d265ed41b151(merge ref)
Refrefs/pull/9/merge
Timestamp

The record is egress-centric; processes without recorded egress do not appear.

Put the record on your pull requests

Garnet records what your code actually did when it ran — one step in your GitHub Actions workflow.

Read the docs