[source-github] Destination Process Exits with Code 143 After Upgrading to Latest Experimental Airbyte Version

### Connector Name

source-github

### Connector Version

2.1.30

### What step the error happened?

During the sync

### Relevant information

## Description

We are testing the GitHub connector on the latest experimental Airbyte version.

Previously, we observed extremely high memory consumption during large GitHub syncs (approximately 128 GB). While reviewing the recent fixes, we noticed the following change:

> Log event flushing: Fixed an issue where log events could accumulate in memory instead of being flushed, reducing memory overhead.

This issue appeared very similar to what we were experiencing, so we upgraded to the latest experimental version to validate the fix.

## Current Behavior

After upgrading, the previous excessive memory usage is no longer observed. However, the sync now consistently fails with the following error:

```text
2026-06-17 07:21:22,396 [pool-4-thread-4] ERROR i.a.c.o.w.DestinationReader(run):60 - DestinationReader error:

io.airbyte.workers.internal.exception.DestinationException: Destination process exited with non-zero exit code 143

at io.airbyte.container.orchestrator.worker.DestinationReader.run(ReplicationTask.kt:55)

at io.airbyte.container.orchestrator.worker.ReplicationWorker$runJobs$2$tasks$1$1.invokeSuspend(ReplicationWorker.kt:152)

at io.airbyte.container.orchestrator.worker.ReplicationWorker$runJobs$2$tasks$1$1.invoke(ReplicationWorker.kt)

at io.airbyte.container.orchestrator.worker.ReplicationWorker$runJobs$2$tasks$1$1.invoke(ReplicationWorker.kt)

at io.airbyte.container.orchestrator.worker.util.AsyncUtils$runAsync$1$1.invokeSuspend(AsyncUtils.kt:22)

at io.airbyte.container.orchestrator.worker.util.AsyncUtils$runAsync$1$1.invoke(AsyncUtils.kt)

at io.airbyte.container.orchestrator.worker.util.AsyncUtils$runAsync$1$1.invoke(AsyncUtils.kt)

at kotlinx.coroutines.intrinsics.UndispatchedKt.startUndspatched(Undispatched.kt:66)

at kotlinx.coroutines.intrinsics.UndispatchedKt.startUndispatchedOrReturn(Undispatched.kt:43)

at kotlinx.coroutines.BuildersKt__Builders_commonKt.withContext(Builders.common.kt:165)

at kotlinx.coroutines.BuildersKt.withContext(Unknown Source)
```

## Resource Configuration

We have allocated approximately 32 GB of memory to each container involved in the replication job.

However, when the failure occurs:

* Memory usage remains around 2 GB per container.
* No memory spike is observed.
* No OOMKilled events are reported.
* The destination container exits with code 143.
Supported images

### Relevant log output

```shell

```

### Contribute

- [ ] Yes, I want to contribute

---
**Internal Tracking:** https://github.com/airbytehq/oncall/issues/12896

Start with the source-github sync context and the stack-trace entry point in ReplicationTask.kt, especially DestinationReader.run. Review the destination container logs and exit-code handling around the reported code 143, then reproduce the sync with the stated resource configuration. Done means the sync no longer exits 143 unexpectedly and the behavior is covered by an appropriate regression check.

由索引模型根據 Issue 內容生成。