Execution Profile

garnet-labs/pnpm

Recorded at the kernel by Garnetfor commit 29fe69e (merge ref)

Garnet Jibril Release Gate/reproduce

run 34310387514

Execution chains

5 destinations · 6 processes
  • systemd
    • bashbashbashbashRunner.Listener
      • Runner.Worker
        • bash
          • curl[4840 · curl]step: <unknown>
            • registry.npmjs.org104.16.0.34:443 (https) · tcp
            • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • node[4842 · node]step: <unknown>
            • registry.npmjs.org104.16.7.34:443 (https) · tcp
            • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • sudo[4879 · sudo]step: <unknown>
            • localhost127.0.0.53:53 (dns) · udp(dns resolver)
        • node
          • sudo[4828 · sudo]
            • localhost127.0.0.53:53 (dns) · udp(dns resolver)
    • chronyd[1853 · chronyd]
      • 169.254.169.123:123 (ntp) · udp
    • systemd-resolved[1711 · systemd-resolved]
      • 8.8.8.8:53 (dns) · udp
Run details
Repositorygarnet-labs/pnpm
WorkflowGarnet Jibril Release Gate
Jobreproduce
Profile UUID01a08463-3786-7628-bdd8-f5ae4f151e54
Refrefs/pull/43/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.