Execution Profile

garnet-labs/pnpm

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

Garnet Bootstrap Routing/bootstrap-routing

run 37891855420

Execution chains

4 destinations · 4 processes
  • systemd
    • hosted-compute-agentRunner.ListenerRunner.Worker
      • bash
        • bash
          • node[2531 · node]step: First run of the Corepack entry point
            • cdn.npmmirror.com163.181.60.205:443 (https) · tcpalso recorded: cdn.npmmirror.com.w.cdngslb.com
            • localhost127.0.0.53:53 (dns) · udp(dns resolver)
    • systemd-resolved[447 · systemd-resolved]
      • 168.63.129.16:53 (dns) · udp
    • python3.12
      • python3.12[1182 · python3.12]
        • 168.63.129.16:32526, 80 (http) · tcp
    • systemd-networkd[648 · systemd-networkd]
      • ip6-allroutersff02::2:0 (reserved) · icmpv6
Run details
Repositorygarnet-labs/pnpm
WorkflowGarnet Bootstrap Routing
Jobbootstrap-routing
Run ID37891855420
Profile UUID01a11f46-777f-7d1b-b0b4-819e276a4864
Commit SHAf4c155d4223433235adb2c0c4568792bf02158d9(merge ref)
Refrefs/pull/108/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