Execution Profile

garnet-labs/pnpm

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

Garnet Bootstrap Routing/bootstrap-routing

run 40563839627

Execution chains

5 destinations · 5 processes
  • systemd
    • hosted-compute-agent
      • Runner.ListenerRunner.Worker
        • bash
          • bash
            • node[2744 · node]step: First run of the Corepack entry point
              • registry.npmjs.org104.16.5.34:443 (https) · tcp
              • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • sudo
        • provjobd3765558749[2081 · provjobd3765558749]
          • 140.82.112.24:443 (https) · tcp
    • systemd-resolved[586 · systemd-resolved]
      • 168.63.129.16:53 (dns) · udp
    • python3.12
      • python3.12[1455 · python3.12]
        • 168.63.129.16:32526, 80 (http) · tcp
    • systemd-networkd[722 · systemd-networkd]
      • ip6-allroutersff02::2:0 (reserved) · icmpv6
Run details
Repositorygarnet-labs/pnpm
WorkflowGarnet Bootstrap Routing
Jobbootstrap-routing
Run ID40563839627
Profile UUID01a17eb4-cdab-744e-b95f-b66257478570
Commit SHAe3ee07a5da3e9dadca2ca56703e76929b21a6530(merge ref)
Refrefs/pull/120/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