Execution Profile

garnet-labs/airbyte

Recorded at the kernel by Garnetfor commit 2c1f4d1 (merge ref)

Connector dependency install and unit tests/install-test

run 43587072320

Execution chains

10 destinations · 7 processes
  • systemd
    • hosted-compute-agent[2084 · hosted-compute-agent]
      • Runner.ListenerRunner.Worker
        • bash
          • poetry[2708 · 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[2833 · pytest]
            • common-external-ingress-999833429.us-east-134.206.136.175:443 (https) · tcpalso recorded: packages.unstructured.io, telemetry.reo.dev
            • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • sudo
        • sudo[2103 · sudo]
          • 20.75.202.224:443 (https) · tcp
      • 20.75.202.224:443 (https) · tcp
    • systemd[521 · 729 · systemd]
      • systemd[1397 · systemd]
        • 168.63.129.16:32526, 80 (http) · tcp
        • 169.254.169.254:80 (http) · tcp(cloud metadata)
      • 168.63.129.16:53 (dns) · udp
      • ip6-allroutersff02::2:0 (reserved) · icmpv6
Run details
Repositorygarnet-labs/airbyte
WorkflowConnector dependency install and unit tests
Jobinstall-test
Run ID43587072320
Profile UUID01a1d9ae-7933-7cc7-92e2-3df8d20f0cc8
Commit SHA2c1f4d17026402a656439baf5fab7ba1034b3f29(merge ref)
Refrefs/pull/18/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