Execution Profile

garnet-labs/pnpm

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

Garnet Jibril Release Gate/reproduce

run 35958123201

Execution chains

4 destinations · 5 processes
  • systemd
    • bashbashbashbashRunner.Listener
      • Runner.Worker
        • bash
          • curl[4554 · curl]step: Stop the action clock
            • registry.npmjs.org104.16.6.34:443 (https) · tcp
            • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • node[4556 · node]step: Stop the action clock
            • registry.npmjs.org104.16.7.34:443 (https) · tcp
            • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • sudo[4593 · sudo]step: <unknown>
            • localhost127.0.0.53:53 (dns) · udp(dns resolver)
        • node
          • sudo[4659 · sudo]
            • localhost127.0.0.53:53 (dns) · udp(dns resolver)
    • systemd-resolved[1713 · systemd-resolved]
      • 8.8.8.8:53 (dns) · udp
Run details
Repositorygarnet-labs/pnpm
WorkflowGarnet Jibril Release Gate
Jobreproduce
Profile UUID01a0d1ca-df0e-7d1f-a01c-de2c43d9b8df
Refrefs/pull/65/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.