Execution Profile

garnet-labs/pnpm

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

Garnet Bootstrap Routing/bootstrap-routing

run 37892143841

Execution chains

4 destinations · 3 processes
  • systemd
    • hosted-compute-agentRunner.ListenerRunner.Worker
      • bash
        • bash
          • node[2748 · 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)
    • python3.12
      • python3.12[1377 · python3.12]
        • 168.63.129.16:32526, 80 (http) · tcp
    • systemd-resolved[489 · systemd-resolved]
      • 168.63.129.16:53 (dns) · udp
Run details
Repositorygarnet-labs/pnpm
WorkflowGarnet Bootstrap Routing
Jobbootstrap-routing
Run ID37892143841
Profile UUID01a11f49-85df-7b10-9920-04eb1fe32f34
Commit SHAaca666c68d95e3aa2b73c00e536406ca92c05568(merge ref)
Refrefs/pull/113/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