Add missing serializations found during provider tests fixing #41252
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
potiuk
requested review from
dstandish,
hussein-awala,
kaxil,
ashb and
bolkedebruin
as code owners
During AWS provider tests fixing for database isolation, two problems have been found: * Trigger object did not have TriggerPydantic corresponding pydantic object which did not allow the Trigger object to get serialized for Trigger processing * Variable and connection accessors were not restored when Context got deserialized. Related: apache#41067
potiuk
force-pushed
the
fix-missing-serializations-for-database-isolation-mode
branch
from
dd71724
to
e2a852f
Compare
hussein-awala
approved these changes
Aug 4, 2024
jscheffl
approved these changes
Aug 4, 2024
eladkal
approved these changes
Aug 4, 2024
aritra24
approved these changes
Aug 4, 2024
potiuk
deleted the
fix-missing-serializations-for-database-isolation-mode
branch
utkarsharma2
added
the
type:misc/internal
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
During AWS provider tests fixing for database isolation, two problems have been found:
Trigger object did not have TriggerPydantic corresponding pydantic object which did not allow the Trigger object to get serialized for Trigger processing
Variable and connection accessors were not restored when Context got deserialized.
Related: #41067
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in newsfragments.