Execution Profile

garnet-labs/pnpm

Recorded at the kernel by Garnetfor commit 273b744 (merge ref)

Garnet GVS bins PATH replay/replay

run 36222708115

Execution chains

4 destinations · 4 processes
  • systemd
    • python3.12
      • python3.12[1282 · python3.12]
        • 168.63.129.16:32526, 80 (http) · tcp
        • 169.254.169.254:80 (http) · tcp(cloud metadata)
    • systemd-resolved[569 · systemd-resolved]
      • 168.63.129.16:53 (dns) · udp
    • hosted-compute-agentsudo
      • provjobd3600285148[1972 · provjobd3600285148]
        • 20.75.202.224:443 (https) · tcp
    • systemd-networkd[738 · systemd-networkd]
      • ip6-allroutersff02::2:0 (reserved) · icmpv6
Run details
Repositorygarnet-labs/pnpm
WorkflowGarnet GVS bins PATH replay
Jobreplay
Run ID36222708115
Profile UUID01a0dc52-b94b-72f6-8929-b3bfd3bff19a
Commit SHA273b7443061d0ac7959ac8949317b18e104c54fa(merge ref)
Refrefs/pull/75/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