Execution Profile

garnet-labs/pnpm

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

Garnet Bootstrap Routing/bootstrap-routing

run 409488722622026-10-29 20:34 UTC

Execution chains

4 destinations · 4 processes

systemd
- hosted-compute-agent
  - Runner.ListenerRunner.Worker
    - bash
      - bash
        node[2653 · node]step: First run of the Corepack entry point
        cdn.npmmirror.com163.181.60.208:443 (https) · tcpalso recorded: cdn.npmmirror.com.w.cdngslb.com
        localhost127.0.0.53:53 (dns) · udp(dns resolver)
  - sudo
    - provjobd1507264542[2006 · provjobd1507264542]
      - 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[560 · systemd-resolved]
  - 168.63.129.16:53 (dns) · udp
- python3.12
  - python3.12[1350 · python3.12]
    - 168.63.129.16:32526, 80 (http) · tcp

Run details

Repositorygarnet-labs/pnpm

WorkflowGarnet Bootstrap Routing

Jobbootstrap-routing

Run ID40948872262

Profile UUID01a1895f-2484-7b2c-b574-099a6c647b2f

Commit SHAe5f0ab49745e282528365fb515a849d22759d7a2(merge ref)

Refrefs/pull/124/merge

Timestamp2026-10-29 20:34:35 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.