Execution Profile

garnet-labs/pnpm

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

Garnet Bootstrap Routing/bootstrap-routing

run 37849237824

Execution chains

6 destinations · 4 processes
  • systemd
    • hosted-compute-agent
      • Runner.ListenerRunner.Worker
        • bash
          • bash
            • node[2516 · 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
        • provjobd456380582[1873 · provjobd456380582]
          • 20.75.202.224:443 (https) · tcp
    • python3.12
      • python3.12[1398 · python3.12]
        • 168.63.129.16:32526, 80 (http) · tcp
        • 169.254.169.254:80 (http) · tcp(cloud metadata)
    • systemd-resolved[427 · systemd-resolved]
      • 168.63.129.16:53 (dns) · udp
Run details
Repositorygarnet-labs/pnpm
WorkflowGarnet Bootstrap Routing
Jobbootstrap-routing
Run ID37849237824
Profile UUID01a11d7d-7274-778d-88d5-83a0faf868b7
Commit SHAf8ab6d988f34416eaeffd666eac6c72fb39a7159(merge ref)
Refrefs/pull/102/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