Execution Profile

garnet-labs/posthog

Recorded at the kernel by Garnetfor commit 5812b1c (merge ref)

Garnet Runtime Visibility/acceptance-requirements-install

run 42068620121

Execution chains

5 destinations · 4 processes
  • systemd
    • hosted-compute-agent
      • Runner.ListenerRunner.Worker
        • bash
          • python3.12[2700 · python3.12]
            • dualstack.python.map.fastly.net151.101.128.223:443 (https) · tcpalso recorded: files.pythonhosted.org
            • pypi.org151.101.64.223:443 (https) · tcp
            • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • sudo
        • provjobd2252928128[2091 · provjobd2252928128]
          • 140.82.112.23:443 (https) · tcp
    • systemd-resolved[524 · systemd-resolved]
      • 168.63.129.16:53 (dns) · udp
    • python3.12
      • python3.12[1460 · python3.12]
        • 168.63.129.16:32526, 80 (http) · tcp
Run details
Repositorygarnet-labs/posthog
WorkflowGarnet Runtime Visibility
Jobacceptance-requirements-install
Run ID42068620121
Profile UUID01a1aca0-1c97-7c3a-910e-77567fbabba0
Commit SHA5812b1c0193f39c5d61e3af96b7b4cc47b71b8e6(merge ref)
Refrefs/pull/249/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