Execution Profile

garnet-labs/E2B

Recorded at the kernel by Garnetfor commit 5f90022 (merge ref)

Dependency install and test (recorded)/install-test

run 42349021001

Execution chains

15 destinations · 6 processes
  • systemd
    • hosted-compute-[1886 · hosted-compute-]
      • Runner.ListenerRunner.Worker
        • bash
          • node[2451 · node]
            • registry.npmjs.org104.16.0.34:443 (https) · tcp
            • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • sudo
        • provjobd5738173[1920 · provjobd5738173]
          • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • hosted-compute-watchdog-gccus02-01.githubapp140.82.112.23:443 (https) · tcp(github infra)also recorded: glb-2a3c35-public-internal.githubapp.com
      • 140.82.112.24:443 (https) · tcp
    • systemd-resolve[438 · systemd-resolve]
      • 168.63.129.16:53 (dns) · udp
    • python3
      • python3[1196 · python3]
        • 168.63.129.16:32526, 80 (http) · tcp
        • 169.254.169.254:80 (http) · tcp(cloud metadata)
    • systemd-network[649 · systemd-network]
      • ip6-allroutersff02::2:0 (reserved) · icmpv6
Run details
Repositorygarnet-labs/E2B
WorkflowDependency install and test (recorded)
Jobinstall-test
Run ID42349021001
Profile UUID01a1b4ca-dcdd-7c5c-a494-f469daf7175e
Commit SHA5f9002200ff44d6345727852986f7a988dc7a288(merge ref)
Refrefs/pull/55/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