Execution Profile

garnet-labs/pnpm

Recorded at the kernel by Garnetfor commit 8e89eac (merge ref)

Garnet Bootstrap Routing/bootstrap-routing

run 409453003522026-10-29 20:02 UTC

Execution chains

5 destinations · 5 processes

systemd
- hosted-compute-agent
  - Runner.ListenerRunner.Worker
    - bash
      - bash
        node[2768 · node]
        registry.npmjs.org104.16.4.34:443 (https) · tcp
        localhost127.0.0.53:53 (dns) · udp(dns resolver)
  - sudo
    - provjobd2584776802[2072 · provjobd2584776802]
      - localhost127.0.0.53:53 (dns) · udp(dns resolver)
      - hosted-compute-watchdog-prod-iad-02.githubapp140.82.112.24:443 (https) · tcp(github infra)also recorded: glb-2a3c35-public-internal.githubapp.com
- systemd-resolved[537 · systemd-resolved]
  - 168.63.129.16:53 (dns) · udp
- python3.12
  - python3.12[1351 · python3.12]
    - 168.63.129.16:32526, 80 (http) · tcp
- systemd-networkd[731 · systemd-networkd]
  - ip6-allroutersff02::2:0 (reserved) · icmpv6

Run details

Repositorygarnet-labs/pnpm

WorkflowGarnet Bootstrap Routing

Jobbootstrap-routing

Run ID40945300352

Profile UUID01a18941-aee0-721a-aed6-5d8985ca9f4b

Commit SHA8e89eac6c4bce324f9512898112b555e9cc87353(merge ref)

Refrefs/pull/123/merge

Timestamp2026-10-29 20:02:24 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.