Add tests for execute_complete success and error handling in AirbyteTriggerSyncOperator

[SameerMesiah97]

Description

This PR adds unit tests for AirbyteTriggerSyncOperator.execute_complete. The tests cover scenarios where the operator completes successfully on non-error events and where an error event triggers an exception.

Rationale

execute_complete is a key part of the deferrable execution flow but was not previously covered by the test suite. The method contains branching logic based on trigger event status that determines whether execution succeeds or fails.

Notes

• The Airbyte connection has been mocked prematurely to accomodate changes in PR Implement execution_timeout semantics for AirbyteTriggerSyncOperator in deferrable mode #64051. These 2 PRs are forwards-compatible i.e. the changes will work irrespective of the merge order.
• Opportunistically updated exception type from AirflowException to RuntimeError to align with agreed consensus and current implementation, as one of the tests asserts that an error is raised.

[SameerMesiah97]

CI failure is unrelated to my changes. It was present in PR #64084, which only changes the spelling of a 'deferrable' in one of the log messages within the execute method of AirbyteTriggerSyncOperator.

[Copilot]

Pull request overview

Adds unit coverage around the deferrable callback path for the Airbyte provider’s AirbyteTriggerSyncOperator.execute_complete, and updates the operator to raise a different exception type when the trigger reports an error.

Changes:

• Added unit tests for execute_complete covering success-like events and error events.
• Updated AirbyteTriggerSyncOperator.execute_complete to raise RuntimeError on "error" trigger events.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.

File	Description
providers/airbyte/tests/unit/airbyte/operators/test_airbyte.py	Adds tests for AirbyteTriggerSyncOperator.execute_complete outcomes.
providers/airbyte/src/airflow/providers/airbyte/operators/airbyte.py	Changes the exception raised on "error" events in execute_complete.

[potiuk]

@SameerMesiah97 This PR has been converted to draft because it does not yet meet our Pull Request quality criteria.

Issues found:

• ❌ Provider tests: Failing: Postgres tests: providers / DB-prov:Postgres:14:3.10:airbyte,common.compat, MySQL tests: providers / DB-prov:MySQL:8.0:3.10:airbyte,common.compat, Sqlite tests: providers / DB-prov:Sqlite:3.10:airbyte,common.compat. Run provider tests with breeze run pytest <provider-test-path> -xvs. See Provider tests docs.

Note: Your branch is 328 commits behind main. Some check failures may be caused by changes in the base branch rather than by your PR. Please rebase your branch and push again to get up-to-date CI results.

What to do next:

• The comment informs you what you need to do.
• Fix each issue, then mark the PR as "Ready for review" in the GitHub UI - but only after making sure that all the issues are fixed.
• There is no rush — take your time and work at your own pace. We appreciate your contribution and are happy to wait for updates.
• Maintainers will then proceed with a normal review.

Converting a PR to draft is not a rejection — it is an invitation to bring the PR up to the project's standards so that maintainer review time is spent productively. There is no rush — take your time and work at your own pace. We appreciate your contribution and are happy to wait for updates. If you have questions, feel free to ask on the Airflow Slack.

---

Note: This comment was drafted by an AI-assisted triage tool and may contain mistakes. Once you have addressed the points above, an Apache Airflow maintainer — a real person — will take the next look at your PR. We use this two-stage triage process so that our maintainers' limited time is spent where it matters most: the conversation with you.

[Copilot]

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

[SameerMesiah97]

Description

This PR adds unit tests for AirbyteTriggerSyncOperator.execute_complete. The tests cover scenarios where the operator completes successfully on non-error events and where an error event triggers an exception.

Rationale

execute_complete is a key part of the deferrable execution flow but was not previously covered by the test suite. The method contains branching logic based on trigger event status that determines whether execution succeeds or fails.

Notes

• The Airbyte connection has been mocked prematurely to accomodate changes in PR Implement execution_timeout semantics for AirbyteTriggerSyncOperator in deferrable mode #64051. These 2 PRs are forwards-compatible i.e. the changes will work irrespective of the merge order.
• Opportunistically updated exception type from AirflowException to RuntimeError to align with agreed consensus and current implementation, as one of the tests asserts that an error is raised.

[SameerMesiah97]

CI failure is unrelated to my changes. It was present in PR #64084, which only changes the spelling of a 'deferrable' in one of the log messages within the execute method of AirbyteTriggerSyncOperator.

[Copilot]

Pull request overview

Adds unit coverage around the deferrable callback path for the Airbyte provider’s AirbyteTriggerSyncOperator.execute_complete, and updates the operator to raise a different exception type when the trigger reports an error.

Changes:

• Added unit tests for execute_complete covering success-like events and error events.
• Updated AirbyteTriggerSyncOperator.execute_complete to raise RuntimeError on "error" trigger events.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.

File	Description
providers/airbyte/tests/unit/airbyte/operators/test_airbyte.py	Adds tests for AirbyteTriggerSyncOperator.execute_complete outcomes.
providers/airbyte/src/airflow/providers/airbyte/operators/airbyte.py	Changes the exception raised on "error" events in execute_complete.

[potiuk]

@SameerMesiah97 This PR has been converted to draft because it does not yet meet our Pull Request quality criteria.

Issues found:

• ❌ Provider tests: Failing: Postgres tests: providers / DB-prov:Postgres:14:3.10:airbyte,common.compat, MySQL tests: providers / DB-prov:MySQL:8.0:3.10:airbyte,common.compat, Sqlite tests: providers / DB-prov:Sqlite:3.10:airbyte,common.compat. Run provider tests with breeze run pytest <provider-test-path> -xvs. See Provider tests docs.

Note: Your branch is 328 commits behind main. Some check failures may be caused by changes in the base branch rather than by your PR. Please rebase your branch and push again to get up-to-date CI results.

What to do next:

• The comment informs you what you need to do.
• Fix each issue, then mark the PR as "Ready for review" in the GitHub UI - but only after making sure that all the issues are fixed.
• There is no rush — take your time and work at your own pace. We appreciate your contribution and are happy to wait for updates.
• Maintainers will then proceed with a normal review.

Converting a PR to draft is not a rejection — it is an invitation to bring the PR up to the project's standards so that maintainer review time is spent productively. There is no rush — take your time and work at your own pace. We appreciate your contribution and are happy to wait for updates. If you have questions, feel free to ask on the Airflow Slack.

---

Note: This comment was drafted by an AI-assisted triage tool and may contain mistakes. Once you have addressed the points above, an Apache Airflow maintainer — a real person — will take the next look at your PR. We use this two-stage triage process so that our maintainers' limited time is spent where it matters most: the conversation with you.

[Copilot]

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

[SameerMesiah97]

Description

This PR adds unit tests for AirbyteTriggerSyncOperator.execute_complete. The tests cover scenarios where the operator completes successfully on non-error events and where an error event triggers an exception.

Rationale

execute_complete is a key part of the deferrable execution flow but was not previously covered by the test suite. The method contains branching logic based on trigger event status that determines whether execution succeeds or fails.

Notes

• The Airbyte connection has been mocked prematurely to accomodate changes in PR Implement execution_timeout semantics for AirbyteTriggerSyncOperator in deferrable mode #64051. These 2 PRs are forwards-compatible i.e. the changes will work irrespective of the merge order.
• Opportunistically updated exception type from AirflowException to RuntimeError to align with agreed consensus and current implementation, as one of the tests asserts that an error is raised.

[SameerMesiah97]

CI failure is unrelated to my changes. It was present in PR #64084, which only changes the spelling of a 'deferrable' in one of the log messages within the execute method of AirbyteTriggerSyncOperator.

[Copilot]

Pull request overview

Adds unit coverage around the deferrable callback path for the Airbyte provider’s AirbyteTriggerSyncOperator.execute_complete, and updates the operator to raise a different exception type when the trigger reports an error.

Changes:

• Added unit tests for execute_complete covering success-like events and error events.
• Updated AirbyteTriggerSyncOperator.execute_complete to raise RuntimeError on "error" trigger events.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.

File	Description
providers/airbyte/tests/unit/airbyte/operators/test_airbyte.py	Adds tests for AirbyteTriggerSyncOperator.execute_complete outcomes.
providers/airbyte/src/airflow/providers/airbyte/operators/airbyte.py	Changes the exception raised on "error" events in execute_complete.

[potiuk]

@SameerMesiah97 This PR has been converted to draft because it does not yet meet our Pull Request quality criteria.

Issues found:

• ❌ Provider tests: Failing: Postgres tests: providers / DB-prov:Postgres:14:3.10:airbyte,common.compat, MySQL tests: providers / DB-prov:MySQL:8.0:3.10:airbyte,common.compat, Sqlite tests: providers / DB-prov:Sqlite:3.10:airbyte,common.compat. Run provider tests with breeze run pytest <provider-test-path> -xvs. See Provider tests docs.

Note: Your branch is 328 commits behind main. Some check failures may be caused by changes in the base branch rather than by your PR. Please rebase your branch and push again to get up-to-date CI results.

What to do next:

• The comment informs you what you need to do.
• Fix each issue, then mark the PR as "Ready for review" in the GitHub UI - but only after making sure that all the issues are fixed.
• There is no rush — take your time and work at your own pace. We appreciate your contribution and are happy to wait for updates.
• Maintainers will then proceed with a normal review.

Converting a PR to draft is not a rejection — it is an invitation to bring the PR up to the project's standards so that maintainer review time is spent productively. There is no rush — take your time and work at your own pace. We appreciate your contribution and are happy to wait for updates. If you have questions, feel free to ask on the Airflow Slack.

---

Note: This comment was drafted by an AI-assisted triage tool and may contain mistakes. Once you have addressed the points above, an Apache Airflow maintainer — a real person — will take the next look at your PR. We use this two-stage triage process so that our maintainers' limited time is spent where it matters most: the conversation with you.

[Copilot]

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

[SameerMesiah97]

Description

This PR adds unit tests for AirbyteTriggerSyncOperator.execute_complete. The tests cover scenarios where the operator completes successfully on non-error events and where an error event triggers an exception.

Rationale

execute_complete is a key part of the deferrable execution flow but was not previously covered by the test suite. The method contains branching logic based on trigger event status that determines whether execution succeeds or fails.

Notes

• The Airbyte connection has been mocked prematurely to accomodate changes in PR Implement execution_timeout semantics for AirbyteTriggerSyncOperator in deferrable mode #64051. These 2 PRs are forwards-compatible i.e. the changes will work irrespective of the merge order.
• Opportunistically updated exception type from AirflowException to RuntimeError to align with agreed consensus and current implementation, as one of the tests asserts that an error is raised.

[SameerMesiah97]

CI failure is unrelated to my changes. It was present in PR #64084, which only changes the spelling of a 'deferrable' in one of the log messages within the execute method of AirbyteTriggerSyncOperator.

[Copilot]

Pull request overview

Adds unit coverage around the deferrable callback path for the Airbyte provider’s AirbyteTriggerSyncOperator.execute_complete, and updates the operator to raise a different exception type when the trigger reports an error.

Changes:

• Added unit tests for execute_complete covering success-like events and error events.
• Updated AirbyteTriggerSyncOperator.execute_complete to raise RuntimeError on "error" trigger events.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.

File	Description
providers/airbyte/tests/unit/airbyte/operators/test_airbyte.py	Adds tests for AirbyteTriggerSyncOperator.execute_complete outcomes.
providers/airbyte/src/airflow/providers/airbyte/operators/airbyte.py	Changes the exception raised on "error" events in execute_complete.

[potiuk]

@SameerMesiah97 This PR has been converted to draft because it does not yet meet our Pull Request quality criteria.

Issues found:

• ❌ Provider tests: Failing: Postgres tests: providers / DB-prov:Postgres:14:3.10:airbyte,common.compat, MySQL tests: providers / DB-prov:MySQL:8.0:3.10:airbyte,common.compat, Sqlite tests: providers / DB-prov:Sqlite:3.10:airbyte,common.compat. Run provider tests with breeze run pytest <provider-test-path> -xvs. See Provider tests docs.

Note: Your branch is 328 commits behind main. Some check failures may be caused by changes in the base branch rather than by your PR. Please rebase your branch and push again to get up-to-date CI results.

What to do next:

• The comment informs you what you need to do.
• Fix each issue, then mark the PR as "Ready for review" in the GitHub UI - but only after making sure that all the issues are fixed.
• There is no rush — take your time and work at your own pace. We appreciate your contribution and are happy to wait for updates.
• Maintainers will then proceed with a normal review.

Converting a PR to draft is not a rejection — it is an invitation to bring the PR up to the project's standards so that maintainer review time is spent productively. There is no rush — take your time and work at your own pace. We appreciate your contribution and are happy to wait for updates. If you have questions, feel free to ask on the Airflow Slack.

---

Note: This comment was drafted by an AI-assisted triage tool and may contain mistakes. Once you have addressed the points above, an Apache Airflow maintainer — a real person — will take the next look at your PR. We use this two-stage triage process so that our maintainers' limited time is spent where it matters most: the conversation with you.

[Copilot]

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

[SameerMesiah97]

Description

This PR adds unit tests for AirbyteTriggerSyncOperator.execute_complete. The tests cover scenarios where the operator completes successfully on non-error events and where an error event triggers an exception.

Rationale

execute_complete is a key part of the deferrable execution flow but was not previously covered by the test suite. The method contains branching logic based on trigger event status that determines whether execution succeeds or fails.

Notes

• The Airbyte connection has been mocked prematurely to accomodate changes in PR Implement execution_timeout semantics for AirbyteTriggerSyncOperator in deferrable mode #64051. These 2 PRs are forwards-compatible i.e. the changes will work irrespective of the merge order.
• Opportunistically updated exception type from AirflowException to RuntimeError to align with agreed consensus and current implementation, as one of the tests asserts that an error is raised.

[SameerMesiah97]

CI failure is unrelated to my changes. It was present in PR #64084, which only changes the spelling of a 'deferrable' in one of the log messages within the execute method of AirbyteTriggerSyncOperator.

[Copilot]

Pull request overview

Adds unit coverage around the deferrable callback path for the Airbyte provider’s AirbyteTriggerSyncOperator.execute_complete, and updates the operator to raise a different exception type when the trigger reports an error.

Changes:

• Added unit tests for execute_complete covering success-like events and error events.
• Updated AirbyteTriggerSyncOperator.execute_complete to raise RuntimeError on "error" trigger events.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.

File	Description
providers/airbyte/tests/unit/airbyte/operators/test_airbyte.py	Adds tests for AirbyteTriggerSyncOperator.execute_complete outcomes.
providers/airbyte/src/airflow/providers/airbyte/operators/airbyte.py	Changes the exception raised on "error" events in execute_complete.

[potiuk]

@SameerMesiah97 This PR has been converted to draft because it does not yet meet our Pull Request quality criteria.

Issues found:

• ❌ Provider tests: Failing: Postgres tests: providers / DB-prov:Postgres:14:3.10:airbyte,common.compat, MySQL tests: providers / DB-prov:MySQL:8.0:3.10:airbyte,common.compat, Sqlite tests: providers / DB-prov:Sqlite:3.10:airbyte,common.compat. Run provider tests with breeze run pytest <provider-test-path> -xvs. See Provider tests docs.

Note: Your branch is 328 commits behind main. Some check failures may be caused by changes in the base branch rather than by your PR. Please rebase your branch and push again to get up-to-date CI results.

What to do next:

• The comment informs you what you need to do.
• Fix each issue, then mark the PR as "Ready for review" in the GitHub UI - but only after making sure that all the issues are fixed.
• There is no rush — take your time and work at your own pace. We appreciate your contribution and are happy to wait for updates.
• Maintainers will then proceed with a normal review.

Converting a PR to draft is not a rejection — it is an invitation to bring the PR up to the project's standards so that maintainer review time is spent productively. There is no rush — take your time and work at your own pace. We appreciate your contribution and are happy to wait for updates. If you have questions, feel free to ask on the Airflow Slack.

---

Note: This comment was drafted by an AI-assisted triage tool and may contain mistakes. Once you have addressed the points above, an Apache Airflow maintainer — a real person — will take the next look at your PR. We use this two-stage triage process so that our maintainers' limited time is spent where it matters most: the conversation with you.

[Copilot]

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

[SameerMesiah97]

Description

This PR adds unit tests for AirbyteTriggerSyncOperator.execute_complete. The tests cover scenarios where the operator completes successfully on non-error events and where an error event triggers an exception.

Rationale

execute_complete is a key part of the deferrable execution flow but was not previously covered by the test suite. The method contains branching logic based on trigger event status that determines whether execution succeeds or fails.

Notes

• The Airbyte connection has been mocked prematurely to accomodate changes in PR Implement execution_timeout semantics for AirbyteTriggerSyncOperator in deferrable mode #64051. These 2 PRs are forwards-compatible i.e. the changes will work irrespective of the merge order.
• Opportunistically updated exception type from AirflowException to RuntimeError to align with agreed consensus and current implementation, as one of the tests asserts that an error is raised.

[SameerMesiah97]

CI failure is unrelated to my changes. It was present in PR #64084, which only changes the spelling of a 'deferrable' in one of the log messages within the execute method of AirbyteTriggerSyncOperator.

[Copilot]

Pull request overview

Adds unit coverage around the deferrable callback path for the Airbyte provider’s AirbyteTriggerSyncOperator.execute_complete, and updates the operator to raise a different exception type when the trigger reports an error.

Changes:

• Added unit tests for execute_complete covering success-like events and error events.
• Updated AirbyteTriggerSyncOperator.execute_complete to raise RuntimeError on "error" trigger events.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.

File	Description
providers/airbyte/tests/unit/airbyte/operators/test_airbyte.py	Adds tests for AirbyteTriggerSyncOperator.execute_complete outcomes.
providers/airbyte/src/airflow/providers/airbyte/operators/airbyte.py	Changes the exception raised on "error" events in execute_complete.

[potiuk]

@SameerMesiah97 This PR has been converted to draft because it does not yet meet our Pull Request quality criteria.

Issues found:

• ❌ Provider tests: Failing: Postgres tests: providers / DB-prov:Postgres:14:3.10:airbyte,common.compat, MySQL tests: providers / DB-prov:MySQL:8.0:3.10:airbyte,common.compat, Sqlite tests: providers / DB-prov:Sqlite:3.10:airbyte,common.compat. Run provider tests with breeze run pytest <provider-test-path> -xvs. See Provider tests docs.

Note: Your branch is 328 commits behind main. Some check failures may be caused by changes in the base branch rather than by your PR. Please rebase your branch and push again to get up-to-date CI results.

What to do next:

• The comment informs you what you need to do.
• Fix each issue, then mark the PR as "Ready for review" in the GitHub UI - but only after making sure that all the issues are fixed.
• There is no rush — take your time and work at your own pace. We appreciate your contribution and are happy to wait for updates.
• Maintainers will then proceed with a normal review.

Converting a PR to draft is not a rejection — it is an invitation to bring the PR up to the project's standards so that maintainer review time is spent productively. There is no rush — take your time and work at your own pace. We appreciate your contribution and are happy to wait for updates. If you have questions, feel free to ask on the Airflow Slack.

---

Note: This comment was drafted by an AI-assisted triage tool and may contain mistakes. Once you have addressed the points above, an Apache Airflow maintainer — a real person — will take the next look at your PR. We use this two-stage triage process so that our maintainers' limited time is spent where it matters most: the conversation with you.

[Copilot]

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

[SameerMesiah97]

Description

This PR adds unit tests for AirbyteTriggerSyncOperator.execute_complete. The tests cover scenarios where the operator completes successfully on non-error events and where an error event triggers an exception.

Rationale

execute_complete is a key part of the deferrable execution flow but was not previously covered by the test suite. The method contains branching logic based on trigger event status that determines whether execution succeeds or fails.

Notes

• The Airbyte connection has been mocked prematurely to accomodate changes in PR Implement execution_timeout semantics for AirbyteTriggerSyncOperator in deferrable mode #64051. These 2 PRs are forwards-compatible i.e. the changes will work irrespective of the merge order.
• Opportunistically updated exception type from AirflowException to RuntimeError to align with agreed consensus and current implementation, as one of the tests asserts that an error is raised.

[SameerMesiah97]

CI failure is unrelated to my changes. It was present in PR #64084, which only changes the spelling of a 'deferrable' in one of the log messages within the execute method of AirbyteTriggerSyncOperator.

[Copilot]

Pull request overview

Adds unit coverage around the deferrable callback path for the Airbyte provider’s AirbyteTriggerSyncOperator.execute_complete, and updates the operator to raise a different exception type when the trigger reports an error.

Changes:

• Added unit tests for execute_complete covering success-like events and error events.
• Updated AirbyteTriggerSyncOperator.execute_complete to raise RuntimeError on "error" trigger events.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.

File	Description
providers/airbyte/tests/unit/airbyte/operators/test_airbyte.py	Adds tests for AirbyteTriggerSyncOperator.execute_complete outcomes.
providers/airbyte/src/airflow/providers/airbyte/operators/airbyte.py	Changes the exception raised on "error" events in execute_complete.

[potiuk]

@SameerMesiah97 This PR has been converted to draft because it does not yet meet our Pull Request quality criteria.

Issues found:

• ❌ Provider tests: Failing: Postgres tests: providers / DB-prov:Postgres:14:3.10:airbyte,common.compat, MySQL tests: providers / DB-prov:MySQL:8.0:3.10:airbyte,common.compat, Sqlite tests: providers / DB-prov:Sqlite:3.10:airbyte,common.compat. Run provider tests with breeze run pytest <provider-test-path> -xvs. See Provider tests docs.

Note: Your branch is 328 commits behind main. Some check failures may be caused by changes in the base branch rather than by your PR. Please rebase your branch and push again to get up-to-date CI results.

What to do next:

• The comment informs you what you need to do.
• Fix each issue, then mark the PR as "Ready for review" in the GitHub UI - but only after making sure that all the issues are fixed.
• There is no rush — take your time and work at your own pace. We appreciate your contribution and are happy to wait for updates.
• Maintainers will then proceed with a normal review.

Converting a PR to draft is not a rejection — it is an invitation to bring the PR up to the project's standards so that maintainer review time is spent productively. There is no rush — take your time and work at your own pace. We appreciate your contribution and are happy to wait for updates. If you have questions, feel free to ask on the Airflow Slack.

---

Note: This comment was drafted by an AI-assisted triage tool and may contain mistakes. Once you have addressed the points above, an Apache Airflow maintainer — a real person — will take the next look at your PR. We use this two-stage triage process so that our maintainers' limited time is spent where it matters most: the conversation with you.

[Copilot]

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

[SameerMesiah97]

Description

This PR adds unit tests for AirbyteTriggerSyncOperator.execute_complete. The tests cover scenarios where the operator completes successfully on non-error events and where an error event triggers an exception.

Rationale

execute_complete is a key part of the deferrable execution flow but was not previously covered by the test suite. The method contains branching logic based on trigger event status that determines whether execution succeeds or fails.

Notes

• The Airbyte connection has been mocked prematurely to accomodate changes in PR Implement execution_timeout semantics for AirbyteTriggerSyncOperator in deferrable mode #64051. These 2 PRs are forwards-compatible i.e. the changes will work irrespective of the merge order.
• Opportunistically updated exception type from AirflowException to RuntimeError to align with agreed consensus and current implementation, as one of the tests asserts that an error is raised.

[SameerMesiah97]

CI failure is unrelated to my changes. It was present in PR #64084, which only changes the spelling of a 'deferrable' in one of the log messages within the execute method of AirbyteTriggerSyncOperator.

[Copilot]

Pull request overview

Adds unit coverage around the deferrable callback path for the Airbyte provider’s AirbyteTriggerSyncOperator.execute_complete, and updates the operator to raise a different exception type when the trigger reports an error.

Changes:

• Added unit tests for execute_complete covering success-like events and error events.
• Updated AirbyteTriggerSyncOperator.execute_complete to raise RuntimeError on "error" trigger events.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.

File	Description
providers/airbyte/tests/unit/airbyte/operators/test_airbyte.py	Adds tests for AirbyteTriggerSyncOperator.execute_complete outcomes.
providers/airbyte/src/airflow/providers/airbyte/operators/airbyte.py	Changes the exception raised on "error" events in execute_complete.

[potiuk]

@SameerMesiah97 This PR has been converted to draft because it does not yet meet our Pull Request quality criteria.

Issues found:

• ❌ Provider tests: Failing: Postgres tests: providers / DB-prov:Postgres:14:3.10:airbyte,common.compat, MySQL tests: providers / DB-prov:MySQL:8.0:3.10:airbyte,common.compat, Sqlite tests: providers / DB-prov:Sqlite:3.10:airbyte,common.compat. Run provider tests with breeze run pytest <provider-test-path> -xvs. See Provider tests docs.

Note: Your branch is 328 commits behind main. Some check failures may be caused by changes in the base branch rather than by your PR. Please rebase your branch and push again to get up-to-date CI results.

What to do next:

• The comment informs you what you need to do.
• Fix each issue, then mark the PR as "Ready for review" in the GitHub UI - but only after making sure that all the issues are fixed.
• There is no rush — take your time and work at your own pace. We appreciate your contribution and are happy to wait for updates.
• Maintainers will then proceed with a normal review.

Converting a PR to draft is not a rejection — it is an invitation to bring the PR up to the project's standards so that maintainer review time is spent productively. There is no rush — take your time and work at your own pace. We appreciate your contribution and are happy to wait for updates. If you have questions, feel free to ask on the Airflow Slack.

---

Note: This comment was drafted by an AI-assisted triage tool and may contain mistakes. Once you have addressed the points above, an Apache Airflow maintainer — a real person — will take the next look at your PR. We use this two-stage triage process so that our maintainers' limited time is spent where it matters most: the conversation with you.

[Copilot]

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.