I need to run the system tests and unit tests .I’ll do all this once the connection is stable. It should work fine within 24 hours.

If I can’t run system tests, I’ll run unit tests instead, fix the issue, and ask someone to run the system tests.
(Please wait a couple of days while I fix the system tests.)

@shahar1 it pass unit tests but system tests failed :

I tried in breeze container with pytest --system file but it will take some time - Related PR - here

I read this - here and tried to run it

I'm working on it and get back to you soon

@Prab-27 A few things need addressing before review — see our Pull Request quality criteria.

• ⚠️ Unresolved review comments: This PR has 1 unresolved review thread from maintainers. Please review and resolve all inline review comments before requesting another review. You can resolve a conversation by clicking 'Resolve conversation' on each thread after addressing the feedback. See pull request guidelines.

Note: Your branch is 185 commits behind main. Please rebase and push again to get up-to-date CI results.

No rush.

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.

Thanks @yuseok89 !!
I was occupied and returned yesterday. I’m catching up on pending tasks and will address this shortly
If I couldn't resolve system tests I'll ping you
Apologize for the delay

@Prab-27 This PR was triaged 41 days ago and has drifted — one maintainer thread is still unresolved. Converting to draft — this PR doesn't yet meet our Pull Request quality criteria.

• ❌ Unresolved review comments (1 thread from a maintainer): please walk through each unresolved review thread. Even if a suggestion looks incorrect or irrelevant — and some of them will be, especially any comments left by automated reviewers like GitHub Copilot — it is still the author's responsibility to respond: apply the fix, reply in-thread with a brief explanation of why the suggestion does not apply, or resolve the thread if the feedback is no longer relevant. Leaving threads unaddressed for weeks blocks the PR from moving forward.

See the linked criteria for how to fix each item, then mark the PR "Ready for review". This is not a rejection — just an invitation to bring the PR up to standard. No rush.

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.

Quick follow-up to the triage comment above — one clarification on the "Unresolved review comments" item:

Once you believe a thread has been addressed — whether by pushing a fix, or by replying in-thread with an explanation of why the suggestion doesn't apply — please mark the thread as resolved yourself by clicking the "Resolve conversation" button at the bottom of each thread. Reviewers don't auto-close their own threads, so an addressed-but-unresolved thread reads as "still waiting on the author" and keeps the PR from moving forward. The author doing the resolve-click is the expected convention on this project.

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.

@yuseok89 Would you please test these tests ?
I tried (from this) but couldn't do it !

@shahar1 @Prab-27
I ran the tests for SalesforceToGcsOperator.

Test Screenshots

unwrap_single True

unwrap_single False