Execution Profile

garnet-labs/litellm

Recorded at the kernel by Garnetfor commit 193b5a4 (merge ref)

Garnet Dependency Replay/dashboard-install

run 32552704651

Execution chains

6 destinations · 6 processes
  • systemd
    • hosted-compute-
      • Runner.Listener
        • Runner.Worker
          • bash
            • node
              • registry.npmjs.org104.16.9.34:443 (https) · tcp
              • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • MainThread
            • github.com140.82.116.4:443 (https) · tcp
            • api.github.com140.82.116.5:443 (https) · tcp
            • release-assets.githubusercontent.com185.199.108.133:443 (https) · tcp
            • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • sudo
        • provjobd1628256
          • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • localhost127.0.0.53:53 (dns) · udp(dns resolver)
    • hosted-compute-agentRunner.ListenerRunner.Worker
      • node
        • github.com140.82.116.4:443 (https) · tcp
        • api.github.com140.82.116.5:443 (https) · tcp
        • release-assets.githubusercontent.com185.199.108.133:443 (https) · tcp
        • localhost127.0.0.53:53 (dns) · udp(dns resolver)
    • systemd-network
      • ip6-allroutersff02::2:0 (reserved) · icmpv6
Run details
Repositorygarnet-labs/litellm
WorkflowGarnet Dependency Replay
Jobdashboard-install
Profile UUID01a027d2-3ec7-7cdd-a8f0-89a8d166c55c
Refrefs/pull/36/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.