Skip to content

fix: accept dict checksum on ManifestV12 unit test nodes#94

Open
Sourabhchrs93 wants to merge 1 commit intomainfrom
fix/manifest-v12-unit-test-checksum
Open

fix: accept dict checksum on ManifestV12 unit test nodes#94
Sourabhchrs93 wants to merge 1 commit intomainfrom
fix/manifest-v12-unit-test-checksum

Conversation

@Sourabhchrs93
Copy link
Contributor

Summary

  • dbt 2.0 preview changed unit_tests[].checksum from a plain string to a Checksum object ({"name": "", "checksum": ""})
  • This broke dbt_ingestion celery task for tenants using dbt 2.0 (e.g., docusign integration 21, batch 1232191)
  • Updated Disabled13.checksum and UnitTests.checksum in ManifestV12 from Optional[str] to Optional[Union[str, Checksum]]

Test plan

  • Validated fix parses dict checksum ({"name": "", "checksum": ""}) correctly
  • Validated backward compatibility with string checksum ("abc123")
  • Validated None checksum still works
  • Reproduced exact error against docusign manifest (batch 1232191) on prod worker pod

🤖 Generated with Claude Code

dbt 2.0 preview emits `unit_tests[].checksum` as a `Checksum` object
(`{"name": "", "checksum": ""}`) instead of a plain string. This broke
`dbt_ingestion` for tenants using dbt 2.0 (e.g., docusign integration 21).

Update `Disabled13.checksum` and `UnitTests.checksum` from
`Optional[str]` to `Optional[Union[str, Checksum]]` to accept both
the old string format and the new dict format.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@Sourabhchrs93 Sourabhchrs93 requested a review from mdesmet March 8, 2026 05:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants