Execution Profile

garnet-labs/pnpm

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

Garnet git prepare skipped-builds replay/replay

run 36223010493

Execution chains

7 destinations · 6 processes
  • systemd
    • hosted-compute-agent
      • Runner.Listener
        • Runner.Worker[2316 · Runner.Worker]
          • bash
            • pnpm[2886 · pnpm]step: <unknown>
              • dash
                • pnpm[2940 · pnpm]
                  • registry.npmjs.org104.16.1.34:443 (https) · tcp
                  • localhost127.0.0.53:53 (dns) · udp(dns resolver)
              • registry.npmjs.org104.16.2.34:443 (https) · tcp
              • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • sudo
        • provjobd811922291[2103 · provjobd811922291]
          • 140.82.112.23:443 (https) · tcp
    • python3.12
      • python3.12[1828 · python3.12]
        • 168.63.129.16:32526, 80 (http) · tcp
    • systemd-resolved[485 · systemd-resolved]
      • 168.63.129.16:53 (dns) · udp
Run details
Repositorygarnet-labs/pnpm
WorkflowGarnet git prepare skipped-builds replay
Jobreplay
Profile UUID01a0dc58-125f-7b91-91ef-7ede83a1e495
Refrefs/pull/81/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.