Execution Profile

garnet-labs/codex

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

Garnet runtime coverage/python-sdk-install

run 33940056246

Execution chains

14 destinations · 4 processes
  • systemd
    • dockerd[1108 · dockerd]
      • registry-1.docker.io100.51.248.20:443 (https) · tcp
      • auth.docker.io172.64.144.78:443 (https) · tcpalso recorded: auth.docker.io.cdn.cloudflare.net
      • d3ipk8a4rcghwr.cloudfront.net3.170.19.20:443 (https) · tcpalso recorded: production.cloudfront.docker.com
      • localhost127.0.0.53:53 (dns) · udp(dns resolver)
    • hosted-compute-agentsudo
      • provjobd3768497344[1822 · provjobd3768497344]
        • localhost127.0.0.53:53 (dns) · udp(dns resolver)
        • hosted-compute-watchdog-prod-iad-02.githubapp140.82.113.24:443 (https) · tcp(github infra)also recorded: glb-2a3c35-public-internal.githubapp.com
    • containerd-shim-runc-v2
      • dash
        • python3.12[2488 · python3.12]
          • pypi.org151.101.0.223:443 (https) · tcp
          • 168.63.129.16:53 (dns) · udp
        • uv[2492 · 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
Profile UUID01a06f77-3fb5-7774-bfab-a26881ed5748
Refrefs/pull/24/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.