Execution Profile

garnet-labs/pnpm

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

Garnet Bootstrap Routing/bootstrap-routing

run 378858007412026-10-09 04:51 UTC

Execution chains

5 destinations · 5 processes

systemd
- hosted-compute-agent
  - Runner.ListenerRunner.Worker
    - bash
      - bash
        node[2663 · node]step: First run of the Corepack entry point
        registry.npmjs.org104.16.10.34:443 (https) · tcp
        localhost127.0.0.53:53 (dns) · udp(dns resolver)
  - sudo
    - provjobd4201110888[2015 · provjobd4201110888]
      - localhost127.0.0.53:53 (dns) · udp(dns resolver)
      - hosted-compute-watchdog-prod-eus-02.githubapp20.75.202.224:443 (https) · tcp(github infra)also recorded: glb-p4a577-public-internal.githubapp.com
- python3.12
  - python3.12[1326 · python3.12]
    - 168.63.129.16:32526, 80 (http) · tcp
- systemd-resolved[541 · systemd-resolved]
  - 168.63.129.16:53 (dns) · udp
- systemd-networkd[737 · systemd-networkd]
  - ip6-allroutersff02::2:0 (reserved) · icmpv6

Run details

Repositorygarnet-labs/pnpm

WorkflowGarnet Bootstrap Routing

Jobbootstrap-routing

Run ID37885800741

Profile UUID01a11f00-ebdd-7ad4-a8cc-3b4591bbe873

Commit SHAc280adeda7d3285bd0b300eae7c6ac4f92c1d6c8(merge ref)

Refrefs/pull/101/merge

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