Execution Profile

garnet-labs/codex

Recorded at the kernel by Garnetfor commit 1230be6 (merge ref)

Garnet runtime coverage/python-sdk-install

run 38529597667

Execution chains

16 destinations · 4 processes
  • systemd
    • dockerd[1322 · dockerd]
      • registry-1.docker.io100.57.240.195:443 (https) · tcp
      • auth.docker.io104.18.43.178:443 (https) · tcpalso recorded: auth.docker.io.cdn.cloudflare.net
      • d3ipk8a4rcghwr.cloudfront.net3.168.51.112:443 (https) · tcpalso recorded: production.cloudfront.docker.com
      • localhost127.0.0.53:53 (dns) · udp(dns resolver)
    • hosted-compute-agentsudo
      • provjobd1218454073[2109 · provjobd1218454073]
        • localhost127.0.0.53:53 (dns) · udp(dns resolver)
    • containerd-shim-runc-v2
      • dash
        • uv[2765 · uv]
          • dualstack.python.map.fastly.net140.248.144.223:443 (https) · tcpalso recorded: files.pythonhosted.org
          • 168.63.129.16:53 (dns) · udp
        • python3.12[2761 · python3.12]
          • dualstack.python.map.fastly.net140.248.144.223:443 (https) · tcpalso recorded: files.pythonhosted.org
          • 168.63.129.16:53 (dns) · udp
Run details
Repositorygarnet-labs/codex
WorkflowGarnet runtime coverage
Jobpython-sdk-install
Profile UUID01a13959-9a85-7b48-9228-9f5b0084a190
Refrefs/pull/30/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.