Move template field validation out of __init__ for Papermill operator (#70296) - #70357
Move template field validation out of __init__ for Papermill operator (#70296)#70357AmoghAtreya wants to merge 1 commit into
Conversation
|
Congratulations on your first Pull Request and welcome to the Apache Airflow community! If you have any issues or are unsure about any anything please check our Contributors' Guide
|
shahar1
left a comment
There was a problem hiding this comment.
Please fix static checks
7491d37 to
0ab078f
Compare
|
Should be fixed now @shahar1 |
|
I think the Mergeable check is struck and needs to be retriggered, is there any way you can retrigger just that one on the admin end or should I close and reopen the PR to re-run checks? Other than that, all checks are passing. @shahar1 |
Ignore this for now, the other checks are those that are important. I'll review soon. |
|
@shahar1 please let me know if there's anything else you want me to fix! |
It seems that you accidentally deleted existing tests from providers/cohere/tests/unit/cohere/operators/test_embedding.py - please try to revert that |
Template fields are rendered after the constructor runs, so validating input_nb and output_nb in __init__ acts on the un-rendered Jinja expression. Defer the checks to execute() and drop the class from the validate-operators-init exemption list. Co-authored-by: Cursor <cursoragent@cursor.com>
c484cb1 to
3db70c4
Compare
Sorry, just fixed that |
|
Apparently #70435 was created first and already merged. |
Description
Refactored
CohereEmbeddingOperatorandPapermillOperatorto ensure template fields are validated during execution or render time rather than inside__init__, aligning with Airflow operator standards.__init__.CohereEmbeddingOperatorandPapermillOperatorentries fromscripts/ci/prek/validate_operators_init_exemptions.txt.Related Issue
works on: #70296
Was generative AI tooling used to co-author this PR?
Generated-by: Gemini following the guidelines