Execution Profile

garnet-labs/pnpm

Recorded at the kernel by Garnetfor commit 4b7cc9f (merge ref)

Garnet Bootstrap Routing/bootstrap-routing

run 40557516326

Execution chains

4 destinations · 3 processes
  • systemd
    • hosted-compute-agentRunner.ListenerRunner.Worker
      • bash
        • bash
          • node[2520 · node]
            • registry.npmjs.org104.16.8.34:443 (https) · tcp
            • localhost127.0.0.53:53 (dns) · udp(dns resolver)
    • python3.12
      • python3.12[1222 · python3.12]
        • 168.63.129.16:32526, 80 (http) · tcp
        • 169.254.169.254:80 (http) · tcp(cloud metadata)
    • systemd-resolved[456 · systemd-resolved]
      • 168.63.129.16:53 (dns) · udp
Run details
Repositorygarnet-labs/pnpm
WorkflowGarnet Bootstrap Routing
Jobbootstrap-routing
Run ID40557516326
Profile UUID01a17e8f-8594-7a0b-8c0a-4d9096427a49
Commit SHA4b7cc9f2930525d957133e51aa9bf060f803b60c(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