Execution Profile

garnet-labs/codex

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

Garnet runtime coverage/python-sdk-install

run 33090277195

Execution chains

13 destinations · 4 processes
  • systemd
    • dockerd[1235 · dockerd]
      • auth.docker.io104.18.43.178:443 (https) · tcpalso recorded: auth.docker.io.cdn.cloudflare.net
      • registry-1.docker.io3.230.250.220:443 (https) · tcp
      • d3ipk8a4rcghwr.cloudfront.net52.85.151.66:443 (https) · tcpalso recorded: production.cloudfront.docker.com
      • localhost127.0.0.53:53 (dns) · udp(dns resolver)
    • hosted-compute-agentsudo
      • provjobd2403458810[2036 · provjobd2403458810]
        • localhost127.0.0.53:53 (dns) · udp(dns resolver)
    • containerd-shim-runc-v2
      • dash
        • python3.12[2699 · python3.12]
          • pypi.org151.101.0.223:443 (https) · tcp
          • 168.63.129.16:53 (dns) · udp
        • uv[2703 · 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 ID33090277195
Profile UUID01a043ed-b6d4-7aaf-a999-4c03aea1ee99
Commit SHAa045a11ab886c35f66783970c3cc61c116109c51(merge ref)
Refrefs/pull/19/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