Execution Profile

garnet-labs/pnpm

Recorded at the kernel by Garnetfor commit 04a5ef0 (merge ref)

Garnet Bootstrap Routing/bootstrap-routing

run 37888386712

Execution chains

4 destinations · 5 processes
  • systemd
    • hosted-compute-agentRunner.Listener
      • Runner.Worker[2223 · Runner.Worker]
        • bash
          • bash
            • node[2789 · node]step: First run of the Corepack entry point
              • registry.npmjs.org104.16.7.34:443 (https) · tcp
              • localhost127.0.0.53:53 (dns) · udp(dns resolver)
        • localhost127.0.0.53:53 (dns) · udp(dns resolver)
    • systemd-resolved[524 · systemd-resolved]
      • 168.63.129.16:53 (dns) · udp
    • python3.12
      • python3.12[2133 · python3.12]
        • 168.63.129.16:32526, 80 (http) · tcp
    • systemd-networkd[740 · systemd-networkd]
      • ip6-allroutersff02::2:0 (reserved) · icmpv6
Run details
Repositorygarnet-labs/pnpm
WorkflowGarnet Bootstrap Routing
Jobbootstrap-routing
Profile UUID01a11f1f-21ac-7706-b3fc-bc74e1f4cc7a
Refrefs/pull/109/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.