Execution Profile

garnet-labs/posthog

Recorded at the kernel by Garnetfor commit 6dfa0e0 (merge ref)

Garnet Runtime Visibility/acceptance-requirements-install

run 431637422562026-11-12 05:48 UTC

Execution chains

7 destinations · 6 processes

systemd
- hosted-compute-agent[2408 · hosted-compute-agent]
  - Runner.ListenerRunner.Worker
    - bash
      - python3.12[2976 · python3.12]step: Install acceptance test requirements (downloads and builds execu
        dualstack.python.map.fastly.net151.101.128.223:443 (https) · tcpalso recorded: files.pythonhosted.org
        localhost127.0.0.100:53 (dns) · udp(dns resolver)
  - sudo
    - provjobd833747427[2423 · provjobd833747427]
      - 20.75.202.224:443 (https) · tcp
  - 20.75.202.224:443 (https) · tcp
- dns-resolver[2003 · dns-resolver]
  - localhost127.0.0.2:443 (https) · tcp
  - localhost127.0.0.53:53 (dns) · udp(dns resolver)
- systemd-resolved[2277 · systemd-resolved]
  - 168.63.129.16:53 (dns) · udp
- python3.12
  - python3.12[1307 · python3.12]
    - 168.63.129.16:32526, 80 (http) · tcp

Run details

Repositorygarnet-labs/posthog

WorkflowGarnet Runtime Visibility

Jobacceptance-requirements-install

Run ID43163742256

Profile UUID01a1ce4d-5d86-72f4-b3e2-a5d2523e5a90

Commit SHA6dfa0e0f2b3d10e44da09c4ce198da2dc6bf9f77(merge ref)

Refrefs/pull/260/merge

Timestamp2026-11-12 05:48:56 UTC

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.