Execution Profile

garnet-labs/pnpm

Recorded at the kernel by Garnetfor commit 1682bff (merge ref)

Garnet Bootstrap Routing/bootstrap-routing

run 40739390987

Execution chains

5 destinations · 4 processes
  • systemd
    • hosted-compute-agentRunner.Listener
      • Runner.Worker[2177 · Runner.Worker]
        • bash
          • bash
            • node[2755 · 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)
        • localhost127.0.0.53:53 (dns) · udp(dns resolver)
    • systemd-resolved[554 · systemd-resolved]
      • 168.63.129.16:53 (dns) · udp
    • python3.12
      • python3.12[1446 · python3.12]
        • 168.63.129.16:32526, 80 (http) · tcp
        • 169.254.169.254:80 (http) · tcp(cloud metadata)
Run details
Repositorygarnet-labs/pnpm
WorkflowGarnet Bootstrap Routing
Jobbootstrap-routing
Run ID40739390987
Profile UUID01a183a2-ce55-71a0-a41e-4fcaec89fb1f
Commit SHA1682bff277e849917f11c872075c6a69354f51a7(merge ref)
Refrefs/pull/122/merge
Timestamp

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.

Read the docs