Execution Profile

garnet-labs/E2B

Recorded at the kernel by Garnetfor commit d4c2518 (merge ref)

Dependency install and test (recorded)/install-test

run 42265316919

Execution chains

14 destinations · 6 processes
  • systemd
    • hosted-compute-[2089 · hosted-compute-]
      • Runner.ListenerRunner.Worker
        • bash
          • node[2722 · node]step: Test
            • registry.npmjs.org104.16.1.34:443 (https) · tcp
            • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • sudo
        • provjobd2952368[2113 · provjobd2952368]
          • 20.75.202.224:443 (https) · tcp
      • 20.75.202.224:443 (https) · tcp
    • python3
      • python3[1382 · python3]
        • 168.63.129.16:32526, 80 (http) · tcp
        • 169.254.169.254:80 (http) · tcp(cloud metadata)
    • systemd-resolve[550 · systemd-resolve]
      • 168.63.129.16:53 (dns) · udp
    • systemd-network[731 · systemd-network]
      • ip6-allroutersff02::2:0 (reserved) · icmpv6
Run details
Repositorygarnet-labs/E2B
WorkflowDependency install and test (recorded)
Jobinstall-test
Profile UUID01a1b1fc-f7c1-7cca-b344-a6a481335bf5
Refrefs/pull/11/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.