Execution Profile

garnet-labs/E2B

Recorded at the kernel by Garnetfor commit e9a279f (merge ref)

Dependency install and test (recorded)/install-test

run 42262022126

Execution chains

14 destinations · 6 processes
  • systemd
    • hosted-compute-
      • Runner.Listener
        • Runner.Worker[2005 · Runner.Worker]
          • bash
            • node[2468 · node]
              • registry.npmjs.org104.16.1.34:443 (https) · tcp
              • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • sudo
        • provjobd2498491[1972 · provjobd2498491]
          • 140.82.114.23:443 (https) · tcp
    • systemd-resolve[455 · systemd-resolve]
      • 168.63.129.16:53 (dns) · udp
    • python3
      • python3[1200 · 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 UUID01a1b1e9-acf2-76ad-ac9d-76a4e34befb3
Refrefs/pull/22/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.