Execution Profile

garnet-labs/pnpm

Recorded at the kernel by Garnetfor commit 8f7b66a (merge ref)

Garnet DNS egress/install

run 33937526073

Execution chains

5 destinations · 4 processes
  • systemdbashbashbashbashRunner.Listener
    • Runner.Worker[3613 · Runner.Worker]
      • bash
        • node[4578 · node]step: Install pnpm (npm install -g "pnpm@${PNPM_VERSION}")
          • 104.16.1.34:443 (https) · tcp
          • 8.8.8.8:53 (dns) · udp
        • pnpm[4607 · pnpm]step: Path A - install a two-dependency fixture (cp -r .github/garnet/dns-egress "$RUNNER_TEMP/fixture-install")
          • 104.16.7.34:443 (https) · tcp
          • 8.8.4.4:53 (dns) · udp
          • 8.8.8.8:53 (dns) · udp
        • sudo[4556 · sudo]step: Point resolv.conf at one configured nameserver
          • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • 8.8.8.8:53 (dns) · udp
Run details
Repositorygarnet-labs/pnpm
WorkflowGarnet DNS egress
Jobinstall
Profile UUID01a06f46-67be-7f1e-a077-8d52fae5e810
Refrefs/pull/40/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.