Execution Profile

garnet-labs/pnpm

Recorded at the kernel by Garnetfor commit 2f0cedd (merge ref)

Garnet Bootstrap Routing/bootstrap-routing

run 378804518142026-10-09 03:42 UTC

Execution chains

5 destinations · 5 processes

systemd
- hosted-compute-agent
  - Runner.ListenerRunner.Worker
    - bash
      - bash
        node[2745 · node]step: First run of the Corepack entry point
        registry.npmjs.org104.16.3.34:443 (https) · tcp
        localhost127.0.0.53:53 (dns) · udp(dns resolver)
  - sudo
    - provjobd1853885926[2078 · provjobd1853885926]
      - localhost127.0.0.53:53 (dns) · udp(dns resolver)
      - hosted-compute-watchdog-prod-iad-01.githubapp140.82.112.23:443 (https) · tcp(github infra)also recorded: glb-2a3c35-public-internal.githubapp.com
- python3.12
  - python3.12[1388 · python3.12]
    - 168.63.129.16:32526, 80 (http) · tcp
- systemd-resolved[506 · systemd-resolved]
  - 168.63.129.16:53 (dns) · udp
- systemd-networkd[721 · systemd-networkd]
  - ip6-allroutersff02::2:0 (reserved) · icmpv6

Run details

Repositorygarnet-labs/pnpm

WorkflowGarnet Bootstrap Routing

Jobbootstrap-routing

Run ID37880451814

Profile UUID01a11ec1-8f6e-7d24-bc87-ebbfa77f3a2e

Commit SHA2f0cedd0719ce751e84c57ca3be4c2b78b9ea2c5(merge ref)

Refrefs/pull/102/merge

Timestamp2026-10-09 03:42:42 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.