Execution Profile

garnet-labs/garnet-runtime-review-reference

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

garnet-dependency-replay/record

run 339375419822026-09-05 01:56 UTC

Execution chains

8 destinations · 5 processes

systemd
- hosted-compute-agent
  - Runner.ListenerRunner.Worker
    - bash
      - bash
        node[2520 · node]step: Select commit
        dash
        node[2533 · node]
        api.ipify.org104.26.13.205:443 (https) · tcp
        ip-api.com208.95.112.1:443 (https) · tcp
        httpbin.org54.163.169.7:443 (https) · tcp
        localhost127.0.0.53:53 (dns) · udp(dns resolver)
        registry.npmjs.org104.16.2.34:443 (https) · tcp
        localhost127.0.0.53:53 (dns) · udp(dns resolver)
  - sudo
    - provjobd568428599[2049 · provjobd568428599]
      - 140.82.114.24:443 (https) · tcp
- systemd-resolved[530 · systemd-resolved]
  - 168.63.129.16:53 (dns) · udp
- python3.12
  - python3.12[1368 · python3.12]
    - 168.63.129.16:32526, 80 (http) · tcp
    - 169.254.169.254:80 (http) · tcp(cloud metadata)

Run details

Repositorygarnet-labs/garnet-runtime-review-reference

Workflowgarnet-dependency-replay

Jobrecord

Run ID33937541982

Profile UUID01a06f47-ebed-7501-8095-7176ce66c3df

Commit SHAc64c913069705808c6a4288ad329337ea9e3070e(merge ref)

Refrefs/pull/31/merge

Timestamp2026-09-05 01:56:19 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.