Execution Profile

garnet-labs/litellm

Recorded at the kernel by Garnetfor commit 8003b35 (merge ref)

Dependency install and test (recorded)/install-test

run 42270094822

Execution chains

4 destinations · 5 processes
  • systemd
    • hosted-compute-agentRunner.Listener
      • Runner.Worker[1970 · Runner.Worker]
        • bash
          • node[2420 · node]
            • registry.npmjs.org104.16.1.34:443 (https) · tcp
            • localhost127.0.0.53:53 (dns) · udp(dns resolver)
        • localhost127.0.0.53:53 (dns) · udp(dns resolver)
    • systemd-resolved[439 · systemd-resolved]
      • 168.63.129.16:53 (dns) · udp
    • python3.12
      • python3.12[1341 · python3.12]
        • 168.63.129.16:32526, 80 (http) · tcp
    • systemd-networkd[651 · systemd-networkd]
      • ip6-allroutersff02::2:0 (reserved) · icmpv6
Run details
Repositorygarnet-labs/litellm
WorkflowDependency install and test (recorded)
Jobinstall-test
Run ID42270094822
Profile UUID01a1b219-fd77-7817-853c-972b4dfebc69
Commit SHA8003b356b8e25b45398eed98bc8f892952855744(merge ref)
Refrefs/pull/67/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