Execution Profile

garnet-labs/uv

Recorded at the kernel by Garnetfor commit 3e1c23d (merge ref)

Garnet Runtime Visibility/dep-install

run 42842492050

Execution chains

3 destinations · 4 processes
  • systemd
    • python3.14
      • python3.14[2007 · python3.14]
        • 168.63.129.16:32526, 80 (http) · tcp
    • systemd-resolved[226 · systemd-resolved]
      • 168.63.129.16:53 (dns) · udp
    • hosted-compute-agent[2194 · hosted-compute-agent]
      • sudo
        • provjobd3511218864[2234 · provjobd3511218864]
          • glb-p4a577-public-internal.githubapp.com20.75.202.224:443 (https) · tcp(github infra)also recorded: hosted-compute-request-orchestrator-prod-eus-02
      • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • glb-p4a577-public-internal.githubapp.com20.75.202.224:443 (https) · tcp(github infra)also recorded: hosted-compute-request-orchestrator-prod-eus-02
Run details
Repositorygarnet-labs/uv
WorkflowGarnet Runtime Visibility
Jobdep-install
Profile UUID01a1c60b-cf99-713e-b15f-323c5f489b7e
Refrefs/pull/31/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.