Execution Profile

garnet-labs/E2B

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

Dependency install and test (recorded)/install-test

run 42349026012

Execution chains

16 destinations · 6 processes
  • systemd
    • hosted-compute-[1890 · hosted-compute-]
      • Runner.ListenerRunner.Worker
        • bash
          • node[2415 · node]
            • registry.npmjs.org104.16.0.34:443 (https) · tcp
            • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • sudo
        • provjobd9981672[1906 · provjobd9981672]
          • 140.82.112.24:443 (https) · tcp
      • 140.82.112.23:443 (https) · tcp
    • python3
      • python3[1259 · python3]
        • 168.63.129.16:32526, 80 (http) · tcp
        • 169.254.169.254:80 (http) · tcp(cloud metadata)
    • systemd-resolve[424 · systemd-resolve]
      • 168.63.129.16:53 (dns) · udp
    • systemd-network[648 · systemd-network]
      • ip6-allroutersff02::2:0 (reserved) · icmpv6
Run details
Repositorygarnet-labs/E2B
WorkflowDependency install and test (recorded)
Jobinstall-test
Run ID42349026012
Profile UUID01a1b4ca-da5c-7ac3-a2f0-723be30f55f9
Commit SHAca24f251ab835422c50b5bb88e089009fad810c1(merge ref)
Refrefs/pull/56/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