Execution Profile

garnet-labs/codex

Recorded at the kernel by Garnetfor commit 5e76e05 (merge ref)

blocking-ci/garnet

run 403700087842026-10-26 17:37 UTC

Execution chains

5 destinations · 5 processes

systemd
- hosted-compute-
  - Runner.Listener
    - Runner.Worker[1910 · Runner.Worker]
      - bash
        cargo[2422 · cargo]step: Fetch locked Rust dependencies
        dualstack.k.sni.global.fastly.net140.248.146.137:443 (https) · tcpalso recorded: fastly-index.crates.io, index.crates.io
        github.com140.82.113.3:443 (https) · tcp
        localhost127.0.0.53:53 (dns) · udp(dns resolver)
      - localhost127.0.0.53:53 (dns) · udp(dns resolver)
  - sudo
    - provjobd3068578[1844 · provjobd3068578]
      - localhost127.0.0.53:53 (dns) · udp(dns resolver)
- hosted-compute-agentRunner.ListenerRunner.Worker
  - bash
    - cargo[2422 · cargo]step: Fetch locked Rust dependencies
      - github.com140.82.113.3:443 (https) · tcp
      - localhost127.0.0.53:53 (dns) · udp(dns resolver)
- systemd-network[640 · systemd-network]
  - ip6-allroutersff02::2:0 (reserved) · icmpv6

Run details

Repositorygarnet-labs/codex

Workflowblocking-ci

Jobgarnet

Run ID40370008784

Profile UUID01a1794a-3b92-7304-b79d-4a4b65e00c7d

Commit SHA5e76e05feb8c8f82ed9637fe564b4482a0fd9251(merge ref)

Refrefs/pull/33/merge

Timestamp2026-10-26 17:37:50 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.