Execution Profile

garnet-labs/codex

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

blocking-ci/garnet

run 334053968642026-08-31 14:55 UTC

Execution chains

4 destinations · 4 processes

systemd
- hosted-compute-
  - Runner.Listener
    - Runner.Worker[2139 · Runner.Worker]
      - bash
        cargo[2650 · cargo]step: Fetch locked Rust dependencies
        dualstack.k.sni.global.fastly.net151.101.42.137:443 (https) · tcpalso recorded: fastly-index.crates.io, index.crates.io
        github.com172.182.252.133:443 (https) · tcp
        localhost127.0.0.53:53 (dns) · udp(dns resolver)
      - localhost127.0.0.53:53 (dns) · udp(dns resolver)
  - sudo
    - provjobd2661775[2050 · provjobd2661775]
      - localhost127.0.0.53:53 (dns) · udp(dns resolver)
      - hosted-compute-watchdog-prod-iad-01.githubapp140.82.114.24:443 (https) · tcp(github infra)also recorded: glb-2a3c35-public-internal.githubapp.com
- hosted-compute-agentRunner.ListenerRunner.Worker
  - bash
    - cargo[2650 · cargo]step: Fetch locked Rust dependencies
      - github.com172.182.252.133:443 (https) · tcp
      - localhost127.0.0.53:53 (dns) · udp(dns resolver)

Run details

Repositorygarnet-labs/codex

Workflowblocking-ci

Jobgarnet

Run ID33405396864

Profile UUID01a05851-ed53-7a3e-85fb-7768d75ea5b3

Commit SHAb0aff4141e910f8701f4ac7ab2d20341c6e6ad7e(merge ref)

Refrefs/pull/23/merge

Timestamp2026-08-31 14:55:59 UTC

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.