Execution Profile

garnet-labs/pnpm

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

Garnet Bootstrap Routing/bootstrap-routing

run 37681973669

Execution chains

4 destinations · 4 processes
  • systemd
    • hosted-compute-agent
      • Runner.ListenerRunner.Worker
        • bash
          • bash
            • node[2540 · node]step: First run of the Corepack entry point
              • registry.npmjs.org104.16.9.34:443 (https) · tcp
              • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • sudo
        • provjobd716114743[1876 · provjobd716114743]
          • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • hosted-compute-watchdog-prod-eus-02.githubapp20.75.202.224:443 (https) · tcp(github infra)also recorded: glb-p4a577-public-internal.githubapp.com
    • python3.12
      • python3.12[1224 · python3.12]
        • 168.63.129.16:32526, 80 (http) · tcp
    • systemd-resolved[429 · systemd-resolved]
      • 168.63.129.16:53 (dns) · udp
Run details
Repositorygarnet-labs/pnpm
WorkflowGarnet Bootstrap Routing
Jobbootstrap-routing
Profile UUID01a1180c-18f0-770e-820c-ab503f5d5989
Refrefs/pull/95/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.