Execution Profile

garnet-labs/posthog

Recorded at the kernel by Garnetfor commit 2f52d70 (merge ref)

Garnet Runtime Visibility/clitools-requirements-install

run 43404000155

Execution chains

6 destinations · 3 processes
  • systemd
    • hosted-compute-agentRunner.ListenerRunner.Worker
      • bash
        • python3.12[2658 · python3.12]
          • files.pythonhosted.org140.248.144.223:443 (https) · tcpalso recorded: dualstack.python.map.fastly.net
          • pypi.org151.101.128.223:443 (https) · tcp
          • localhost127.0.0.53:53 (dns) · udp(dns resolver)
    • systemd-resolved[502 · systemd-resolved]
      • 168.63.129.16:53 (dns) · udp
    • systemd-networkd[741 · systemd-networkd]
      • ip6-allroutersff02::2:0 (reserved) · icmpv6
Run details
Repositorygarnet-labs/posthog
WorkflowGarnet Runtime Visibility
Jobclitools-requirements-install
Run ID43404000155
Profile UUID01a1d44d-7b2d-717f-90c6-e68edf08ef20
Commit SHA2f52d707e8a3f9c8666c940e6f6aab1bddb8f51f(merge ref)
Refrefs/pull/263/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