Execution Profile

garnet-labs/pnpm

Recorded at the kernel by Garnetfor commit 10cbcda (merge ref)

Garnet global virtual store slot replay/recorded-ab

run 36223104513

Execution chains

7 destinations · 6 processes
  • systemd
    • hosted-compute-agent[2048 · hosted-compute-agent]
      • Runner.Listener
        • Runner.Worker[2230 · Runner.Worker]
          • bash
            • pnpm[3763 · pnpm]step: <unknown>
              • registry.npmjs.org104.16.10.34:443 (https) · tcp
              • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • sudo
        • provjobd94289459[2067 · provjobd94289459]
          • 140.82.112.24:443 (https) · tcp
      • 140.82.112.23:443 (https) · tcp
      • 140.82.114.24:443 (https) · tcp
    • python3.12
      • python3.12[1495 · python3.12]
        • 168.63.129.16:32526, 80 (http) · tcp
        • 169.254.169.254:80 (http) · tcp(cloud metadata)
    • systemd-resolved[500 · systemd-resolved]
      • 168.63.129.16:53 (dns) · udp
Run details
Repositorygarnet-labs/pnpm
WorkflowGarnet global virtual store slot replay
Jobrecorded-ab
Profile UUID01a0dc5a-0557-77c3-ba03-f9010b46ce03
Refrefs/pull/74/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.