Execution Profile

garnet-labs/express

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

App install/install

run 36815738254

Execution chains

14 destinations · 5 processes
  • systemd
    • hosted-compute-agent
      • Runner.ListenerRunner.Worker
        • bash
          • node[2454 · node]step: Install dependencies (lifecycle scripts execute here)
            • registry.npmjs.org104.16.0.34:443 (https) · tcp
            • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • sudo
        • provjobd2656697824[1964 · provjobd2656697824]
          • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • hosted-compute-watchdog-prod-iad-02.githubapp140.82.112.24:443 (https) · tcp(github infra)also recorded: glb-2a3c35-public-internal.githubapp.com
    • systemd-resolved[521 · systemd-resolved]
      • 168.63.129.16:53 (dns) · udp
    • python3.12
      • python3.12[1305 · python3.12]
        • 168.63.129.16:32526, 80 (http) · tcp
        • 169.254.169.254:80 (http) · tcp(cloud metadata)
    • systemd-networkd[722 · systemd-networkd]
      • ip6-allroutersff02::2:0 (reserved) · icmpv6
Run details
Repositorygarnet-labs/express
WorkflowApp install
Jobinstall
Run ID36815738254
Profile UUID01a0f5be-d212-72ef-a7ab-7c2dc8b1208e
Commit SHAdacc29cd15269bff77d05dbf870c935ac2585378(merge ref)
Refrefs/pull/10/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