Execution Profile

garnet-labs/pnpm

Recorded at the kernel by Garnetfor commit 1b30928 (merge ref)

Garnet Bootstrap Routing/bootstrap-routing

run 37849087501

Execution chains

5 destinations · 4 processes
  • systemd
    • hosted-compute-agent
      • Runner.ListenerRunner.Worker
        • bash
          • bash
            • node[2651 · node]step: First run of the Corepack entry point
              • registry.npmjs.org104.16.6.34:443 (https) · tcp
              • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • sudo
        • provjobd2547846383[2024 · provjobd2547846383]
          • 140.82.113.23:443 (https) · tcp
    • systemd-resolved[602 · systemd-resolved]
      • 168.63.129.16:53 (dns) · udp
    • python3.12
      • python3.12[1416 · python3.12]
        • 168.63.129.16:32526, 80 (http) · tcp
        • 169.254.169.254:80 (http) · tcp(cloud metadata)
Run details
Repositorygarnet-labs/pnpm
WorkflowGarnet Bootstrap Routing
Jobbootstrap-routing
Run ID37849087501
Profile UUID01a11d7c-10da-7391-acc7-4051ed080136
Commit SHA1b30928e141366d1b9abb5e18409d400922eb845(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