Execution Profile

garnet-labs/express

Recorded at the kernel by Garnetfor commit 903e508 (merge ref)

App install/install

run 36820274429

Execution chains

12 destinations · 6 processes
  • systemd
    • hosted-compute-agent
      • Runner.Listener
        • Runner.Worker[2174 · Runner.Worker]
          • bash
            • node[2619 · 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)
          • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • sudo
        • provjobd119311218[2086 · provjobd119311218]
          • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • hosted-compute-watchdog-prod-eus-01.githubapp20.75.202.224:443 (https) · tcp(github infra)also recorded: glb-p4a577-public-internal.githubapp.com
    • systemd-resolved[522 · systemd-resolved]
      • 168.63.129.16:53 (dns) · udp
    • python3.12
      • python3.12[1501 · python3.12]
        • 168.63.129.16:32526, 80 (http) · tcp
        • 169.254.169.254:80 (http) · tcp(cloud metadata)
    • systemd-networkd[721 · systemd-networkd]
      • ip6-allroutersff02::2:0 (reserved) · icmpv6
Run details
Repositorygarnet-labs/express
WorkflowApp install
Jobinstall
Run ID36820274429
Profile UUID01a0f5f4-3d71-75eb-a2c9-d44d12fa1a77
Commit SHA903e5084e4e327eb187536c985fc67638cdd75f4(merge ref)
Refrefs/pull/68/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