Execution Profile

garnet-labs/E2B

Recorded at the kernel by Garnetfor commit 8b6162a (merge ref)

Dependency install and test (recorded)/install-test

run 42269952599

Execution chains

17 destinations · 7 processes
  • systemd
    • hosted-compute-[2086 · hosted-compute-]
      • Runner.Listener
        • Runner.Worker[2176 · Runner.Worker]
          • bash
            • node[2661 · node]step: Test
              • registry.npmjs.org104.16.0.34:443 (https) · tcp
              • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • sudo
        • provjobd2842544[2104 · provjobd2842544]
          • 140.82.114.24:443 (https) · tcp
      • 140.82.114.23: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[530 · systemd-resolve]
      • 168.63.129.16:53 (dns) · udp
    • systemd-network[729 · systemd-network]
      • ip6-allroutersff02::2:0 (reserved) · icmpv6
Run details
Repositorygarnet-labs/E2B
WorkflowDependency install and test (recorded)
Jobinstall-test
Run ID42269952599
Profile UUID01a1b219-bc00-795b-802c-50dc50dca35d
Commit SHA8b6162a5b39bee9e1043e1b2617e5e980e2e0095(merge ref)
Refrefs/pull/48/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