Execution Profile

garnet-labs/pnpm

Recorded at the kernel by Garnetfor commit 01754a8 (merge ref)

Garnet global virtual store slot replay/recorded-ab

run 36222615169

Execution chains

3 destinations · 3 processes
  • systemd
    • hosted-compute-agentRunner.Listener
      • Runner.Worker[2049 · Runner.Worker]
        • localhost127.0.0.53:53 (dns) · udp(dns resolver)
    • systemd-resolved[550 · systemd-resolved]
      • 168.63.129.16:53 (dns) · udp
    • python3.12
      • python3.12[1263 · python3.12]
        • 168.63.129.16:32526, 80 (http) · tcp
        • 169.254.169.254:80 (http) · tcp(cloud metadata)
Run details
Repositorygarnet-labs/pnpm
WorkflowGarnet global virtual store slot replay
Jobrecorded-ab
Run ID36222615169
Profile UUID01a0dc51-14fe-76e7-8fbd-43b75fd7f1e1
Commit SHA01754a812c25945c4ffd0987ce57a9b816320482(merge ref)
Refrefs/pull/74/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.

Read the docs