Execution Profile

garnet-labs/E2B

Recorded at the kernel by Garnetfor commit 4028c53 (merge ref)

Dependency install and test (recorded)/install-test

run 42261951957

Execution chains

12 destinations · 5 processes
  • systemd
    • hosted-compute-[2023 · hosted-compute-]
      • Runner.ListenerRunner.Worker
        • bash
          • node[2567 · node]
            • registry.npmjs.org104.16.10.34:443 (https) · tcp
            • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • sudo
        • provjobd3010056[2042 · provjobd3010056]
          • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • hosted-compute-watchdog-prod-iad-02.githubapp140.82.114.24:443 (https) · tcp(github infra)also recorded: glb-2a3c35-public-internal.githubapp.com
      • 140.82.113.24:443 (https) · tcp
    • systemd-resolve[529 · systemd-resolve]
      • 168.63.129.16:53 (dns) · udp
    • python3
      • python3[1460 · python3]
        • 168.63.129.16:32526, 80 (http) · tcp
        • 169.254.169.254:80 (http) · tcp(cloud metadata)
Run details
Repositorygarnet-labs/E2B
WorkflowDependency install and test (recorded)
Jobinstall-test
Profile UUID01a1b1e8-c4fc-7920-8459-161566b2669b
Refrefs/pull/15/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.