Execution Profile

garnet-labs/codex

Recorded at the kernel by Garnetfor commit 4fc686d (merge ref)

Garnet runtime coverage/python-sdk-install

run 33104808842

Execution chains

13 destinations · 3 processes
  • systemd
    • dockerd[1039 · dockerd]
      • auth.docker.io172.64.144.78:443 (https) · tcpalso recorded: auth.docker.io.cdn.cloudflare.net
      • d3ipk8a4rcghwr.cloudfront.net18.155.173.114:443 (https) · tcpalso recorded: production.cloudfront.docker.com
      • registry-1.docker.io52.202.160.116:443 (https) · tcp
      • localhost127.0.0.53:53 (dns) · udp(dns resolver)
    • containerd-shim-runc-v2
      • dash
        • python3.12[2466 · python3.12]
          • pypi.org151.101.0.223:443 (https) · tcp
          • 168.63.129.16:53 (dns) · udp
        • uv[2471 · uv]
          • pypi.org151.101.0.223:443 (https) · tcp
          • 168.63.129.16:53 (dns) · udp
Run details
Repositorygarnet-labs/codex
WorkflowGarnet runtime coverage
Jobpython-sdk-install
Run ID33104808842
Profile UUID01a04488-a505-764a-a0e0-ba1ecd7744e6
Commit SHA4fc686d06b52f55c8eb589a431b04d32dd52134d(merge ref)
Refrefs/pull/21/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