Execution Profile

garnet-labs/E2B

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

Dependency install and test (recorded)/install-test

run 42262056568

Execution chains

14 destinations · 6 processes
  • systemd
    • hosted-compute-[1795 · hosted-compute-]
      • Runner.ListenerRunner.Worker
        • bash
          • node[2446 · node]
            • registry.npmjs.org104.16.0.34:443 (https) · tcp
            • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • sudo
        • provjobd3456420[1812 · provjobd3456420]
          • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • glb-p4a577-public-internal.githubapp.com20.75.202.224:443 (https) · tcp(github infra)also recorded: hosted-compute-watchdog-prod-eus-01.githubapp
      • glb-p4a577-public-internal.githubapp.com20.75.202.224:443 (https) · tcp(github infra)also recorded: hosted-compute-watchdog-prod-eus-01.githubapp
    • systemd-resolve[511 · systemd-resolve]
      • 168.63.129.16:53 (dns) · udp
    • python3
      • python3[1201 · python3]
        • 168.63.129.16:32526, 80 (http) · tcp
    • systemd-network[659 · systemd-network]
      • ip6-allroutersff02::2:0 (reserved) · icmpv6
Run details
Repositorygarnet-labs/E2B
WorkflowDependency install and test (recorded)
Jobinstall-test
Profile UUID01a1b1ea-35f3-7b8d-9edf-00ebf5aa2269
Refrefs/pull/25/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.