-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove legacy time spine warning message #353
Remove legacy time spine warning message #353
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good - note that we'll need to release a new production version in order to ship this to core. That process is documented here https://www.notion.so/dbtlabs/DSI-Build-Release-Process-48d94828e8b840abb8529f7501fb2c5b?pvs=4
) | ||
issues = validator.validate_semantic_manifest(semantic_manifest) | ||
assert not issues.has_blocking_issues | ||
assert len(issues.warnings) == 1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could keep this test but update this to say assert len(issues.warnings) == 1
and remove the line below!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I assume you mean assert len(issues.warnings) == 0
, right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes 😆
Actually, we shouldn't do the production release until after code freeze, since mantle could pick up the new version. |
Resolves # SL-2934
Description
This PR removes the legacy time spine configuration warning in order to make the warning appear in dbt-core as a behavior change instead.
Checklist
changie new
to create a changelog entry