Execution Profile

garnet-labs/airbyte

Recorded at the kernel by Garnetfor commit 74a8bb0 (merge ref)

Connector dependency install and unit tests/install-test

run 43565578112

Execution chains

10 destinations · 6 processes
  • systemd
    • hosted-compute-agent[2119 · hosted-compute-agent]
      • Runner.ListenerRunner.Worker
        • bash
          • poetry[2763 · poetry]
            • dualstack.python.map.fastly.net151.101.0.223:443 (https) · tcpalso recorded: files.pythonhosted.org
            • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • pytest[2888 · pytest]step: Run connector unit tests
            • common-external-ingress-999833429.us-east-152.23.139.137:443 (https) · tcpalso recorded: packages.unstructured.io, telemetry.reo.dev
            • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • sudo
        • sudo[2142 · sudo]
          • 140.82.112.24:443 (https) · tcp
      • 140.82.112.23:443 (https) · tcp
      • 140.82.114.23:443 (https) · tcp
      • localhost127.0.0.53:53 (dns) · udp(dns resolver)
    • systemd[565 · systemd]
      • systemd[1948 · systemd]
        • 168.63.129.16:32526, 80 (http) · tcp
      • 168.63.129.16:53 (dns) · udp
Run details
Repositorygarnet-labs/airbyte
WorkflowConnector dependency install and unit tests
Jobinstall-test
Run ID43565578112
Profile UUID01a1d8b5-4eab-7fee-8455-e124bb090b1e
Commit SHA74a8bb0a5dbc73b769320c39a4a2674a56a14aff(merge ref)
Refrefs/pull/15/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