Execution Profile

garnet-labs/pnpm

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

Garnet global virtual store slot replay/recorded-ab

run 36223319520

Execution chains

5 destinations · 4 processes
  • systemd
    • hosted-compute-agent
      • Runner.ListenerRunner.Worker
        • bash
          • pnpm[3681 · pnpm]step: <unknown>
            • registry.npmjs.org104.16.1.34:443 (https) · tcp
            • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • sudo
        • provjobd837458933[2034 · provjobd837458933]
          • 140.82.112.23:443 (https) · tcp
    • python3.12
      • python3.12[1755 · python3.12]
        • 168.63.129.16:32526, 80 (http) · tcp
        • 169.254.169.254:80 (http) · tcp(cloud metadata)
    • systemd-resolved[489 · systemd-resolved]
      • 168.63.129.16:53 (dns) · udp
Run details
Repositorygarnet-labs/pnpm
WorkflowGarnet global virtual store slot replay
Jobrecorded-ab
Run ID36223319520
Profile UUID01a0dc5d-e9a5-76ae-bc9e-30c4efa59973
Commit SHAfec5b47a117708da66faa0331c7459c1a0d21e1a(merge ref)
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.

Read the docs