Execution Profile

garnet-labs/E2B

Recorded at the kernel by Garnetfor commit 7446a48 (merge ref)

Dependency install and test (recorded)/install-test

run 42269988250

Execution chains

13 destinations · 6 processes
  • systemd
    • hosted-compute-[1877 · hosted-compute-]
      • Runner.Listener
        • Runner.Worker[1987 · Runner.Worker]
          • bash
            • node[2431 · node]
              • registry.npmjs.org104.16.10.34:443 (https) · tcp
              • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • sudo
        • provjobd3494889[1901 · provjobd3494889]
          • 140.82.114.23:443 (https) · tcp
      • 140.82.112.23:443 (https) · tcp
    • python3
      • python3[1217 · python3]
        • 168.63.129.16:32526, 80 (http) · tcp
    • systemd-resolve[497 · systemd-resolve]
      • 168.63.129.16:53 (dns) · udp
Run details
Repositorygarnet-labs/E2B
WorkflowDependency install and test (recorded)
Jobinstall-test
Run ID42269988250
Profile UUID01a1b219-919f-79e1-8c49-462e452d4360
Commit SHA7446a483e6da7d77296932ceb29d18421f99bf6d(merge ref)
Refrefs/pull/53/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