Execution Profile

garnet-labs/codex

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

Garnet runtime coverage/python-sdk-install

run 39114388442

Execution chains

14 destinations · 3 processes
  • systemd
    • dockerd[1063 · dockerd]
      • registry-1.docker.io100.60.105.131:443 (https) · tcp
      • auth.docker.io172.64.144.78:443 (https) · tcpalso recorded: auth.docker.io.cdn.cloudflare.net
      • d3ipk8a4rcghwr.cloudfront.net18.172.134.3:443 (https) · tcpalso recorded: production.cloudfront.docker.com
      • localhost127.0.0.53:53 (dns) · udp(dns resolver)
    • hosted-compute-agentsudo
      • provjobd2353040170[1893 · provjobd2353040170]
        • localhost127.0.0.53:53 (dns) · udp(dns resolver)
        • hosted-compute-watchdog-prod-iad-01.githubapp140.82.112.24:443 (https) · tcp(github infra)also recorded: glb-2a3c35-public-internal.githubapp.com
    • containerd-shim-runc-v2dash
      • uv[2540 · uv]
        • dualstack.python.map.fastly.net140.248.144.223:443 (https) · tcpalso recorded: files.pythonhosted.org
        • 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 UUID01a14e49-0168-7814-822e-a1fbb0a0f53c
Refrefs/pull/31/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.