Fix duplicate logs in dbt build when source freshness is enabled

[pankajastro]

In DBT_RUNNER mode, run_dbt_runner appended a new XCom-pushing callback to _dbt_runner_callbacks on every invocation. When source rendering is enabled the producer runs dbt source freshness first (via _run_source_freshness), registering a freshness callback, then runs dbt build which appended a second callback. Both callbacks fired for every event during the build, printing each log line twice.

Fix: skip callback registration when context["_check_source_freshness"] is True. The freshness run's results are captured from target/sources.json afterwards and do not need per-event XCom pushes. Raw JSON stdout is still suppressed via _NullWriter for both paths.

Logs Before changes

Logs After changes

closes: #2558

[Copilot]

Pull request overview

Fixes duplicate dbt log lines in WATCHER mode when source freshness pre-check is enabled by preventing dbtRunner callback registration during the freshness run (while still suppressing raw JSON stdout).

Changes:

• Skip registering the XCom/log-parsing dbtRunner callback when context["_check_source_freshness"] is set for the source freshness pre-check.
• Continue suppressing raw --log-format json stdout during both freshness and build runs via _NullWriter.
• Add a regression test ensuring callbacks are not appended during the freshness run.

Reviewed changes

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

File	Description
cosmos/operators/watcher.py	Avoids callback accumulation during source freshness pre-check to prevent duplicate logging during the subsequent build.
tests/operators/test_watcher.py	Adds a targeted test to verify callback registration is skipped when _check_source_freshness is set.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 98.04%. Comparing base (f4fb470) to head (b792b12).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #2564   +/-   ##
=======================================
  Coverage   98.04%   98.04%           
=======================================
  Files         103      103           
  Lines        7586     7589    +3     
=======================================
+ Hits         7438     7441    +3     
  Misses        148      148           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[tatiana]

@pankajastro, thanks for fixing this. Let's add it to the 1.14.1 milestone.

The implementation looks good, minor feedback inline.

Were you able to reproduce the problem via an Airlfow DAG, and then, after this change, confirm it works? If possible, add screenshots of the before-and-after of the change in the PR description.

[Copilot]

Pull request overview

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

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[pankajastro]

Were you able to reproduce the problem via an Airlfow DAG, and then, after this change, confirm it works? If possible, add screenshots of the before-and-after of the change in the PR description.

yes, this happen when invocation_mode: DBT_RUNNER, execution_mode: Watcher, test_behavour: ALL, WITH_TESTS_OR_FRESHNESS. Updated desc with screen