Execution Profile

garnet-labs/pnpm

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

Garnet Bootstrap Routing/bootstrap-routing

run 378857749512026-10-09 04:51 UTC

Execution chains

6 destinations · 4 processes

systemd
- hosted-compute-agent
  - Runner.ListenerRunner.Worker
    - bash
      - bash
        node[2763 · node]step: First run of the Corepack entry point
        cdn.npmmirror.com163.181.60.201:443 (https) · tcpalso recorded: cdn.npmmirror.com.w.cdngslb.com
        localhost127.0.0.53:53 (dns) · udp(dns resolver)
  - sudo
    - provjobd1566406239[2108 · provjobd1566406239]
      - localhost127.0.0.53:53 (dns) · udp(dns resolver)
      - hosted-compute-watchdog-prod-eus-01.githubapp20.75.202.224:443 (https) · tcp(github infra)also recorded: glb-p4a577-public-internal.githubapp.com
- python3.12
  - python3.12[1498 · python3.12]
    - 168.63.129.16:32526, 80 (http) · tcp
    - 169.254.169.254:80 (http) · tcp(cloud metadata)
- systemd-resolved[493 · systemd-resolved]
  - 168.63.129.16:53 (dns) · udp

Run details

Repositorygarnet-labs/pnpm

WorkflowGarnet Bootstrap Routing

Jobbootstrap-routing

Run ID37885774951

Profile UUID01a11f00-b958-7859-babf-c79052390dbb

Commit SHAeccedcadc29421ceaa734c1076552b1500de1f88(merge ref)

Refrefs/pull/102/merge

Timestamp2026-10-09 04:51: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.