Execution Profile

garnet-labs/codex

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

blocking-ci/garnet

run 330970339412026-08-27 17:11 UTC

Execution chains

6 destinations · 4 processes

systemd
- hosted-compute-
  - Runner.ListenerRunner.Worker
    - bash
      - cargo[2583 · cargo]step: Fetch locked Rust dependencies
        github.com140.82.113.4:443 (https) · tcp
        dualstack.k.sni.global.fastly.net146.75.30.137:443 (https) · tcpalso recorded: fastly-index.crates.io, index.crates.io
        localhost127.0.0.53:53 (dns) · udp(dns resolver)
  - sudo
    - sudo[2037 · sudo]
      - localhost127.0.0.53:53 (dns) · udp(dns resolver)
      - hosted-compute-watchdog-prod-iad-01.githubapp140.82.113.24:443 (https) · tcp(github infra)also recorded: glb-2a3c35-public-internal.githubapp.com
- hosted-compute-agentRunner.ListenerRunner.Worker
  - bash
    - cargo[2583 · cargo]step: Fetch locked Rust dependencies
      - github.com140.82.113.4:443 (https) · tcp
      - localhost127.0.0.53:53 (dns) · udp(dns resolver)
- systemd-network[787 · systemd-network]
  - ip6-allroutersff02::2:0 (reserved) · icmpv6

Run details

Repositorygarnet-labs/codex

Workflowblocking-ci

Jobgarnet

Run ID33097033941

Profile UUID01a04434-e144-75e6-b5fc-234cf8b4dff6

Commit SHAb0ad6a5590f88bc1c02f1f945934d265ed41b151(merge ref)

Refrefs/pull/9/merge

Timestamp2026-08-27 17:11:51 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.