Execution Profile

garnet-labs/E2B

Recorded at the kernel by Garnetfor commit 1c4edb5 (merge ref)

Dependency install and test (recorded)/install-test

run 42262110453

Execution chains

15 destinations · 7 processes
  • systemd
    • hosted-compute-[1771 · hosted-compute-]
      • Runner.Listener
        • Runner.Worker[1853 · Runner.Worker]
          • bash
            • node[2411 · node]
              • 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
        • provjobd3955795[1787 · provjobd3955795]
          • 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.113.24:443 (https) · tcp
    • python3
      • python3[1207 · python3]
        • 168.63.129.16:32526, 80 (http) · tcp
    • systemd-resolve[435 · systemd-resolve]
      • 168.63.129.16:53 (dns) · udp
    • systemd-network[658 · systemd-network]
      • ip6-allroutersff02::2:0 (reserved) · icmpv6
Run details
Repositorygarnet-labs/E2B
WorkflowDependency install and test (recorded)
Jobinstall-test
Profile UUID01a1b1ea-bcae-778b-a353-6770aad02461
Refrefs/pull/30/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.