Execution Profile

garnet-labs/pnpm

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

Garnet Proxy Routing/proxy-routing

run 37704065214

Execution chains

5 destinations · 5 processes
  • systemd
    • bashbashbashbashRunner.Listener
      • Runner.Worker
        • bash
          • bash
            • pnpm[15017 · pnpm]step: Ping the registry with proxy=false
              • registry.npmjs.org104.16.6.34:443 (https) · tcp
              • localhost127.0.0.53:53 (dns) · udp(dns resolver)
        • node
          • sudo[14987 · sudo]
            • localhost127.0.0.53:53 (dns) · udp(dns resolver)
    • chronyd[1860 · chronyd]
      • 169.254.169.123:123 (ntp) · udp
    • sudo
      • blacksmithd[2323 · blacksmithd]
        • 192.168.127.1:1034 · tcp
    • systemd-resolved[1721 · systemd-resolved]
      • 8.8.8.8:53 (dns) · udp
Run details
Repositorygarnet-labs/pnpm
WorkflowGarnet Proxy Routing
Jobproxy-routing
Profile UUID01a118c4-1d72-7f5b-a12c-401e832932bb
Refrefs/pull/99/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.