You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 6f424c8
Browse filesBrowse the repository at this point in the historyBrowse files
Let an XCom read tell the value it loads which iteration it came from
loop.previous read an iterated terminal's XComIterable from the previous
iteration, then patched the pointer from outside so its items were read
from that iteration too: an isinstance check in loop.py, and any other read
with previous_iteration (a lazy sequence item) kept the bug.
The XCom read now passes its previous_iteration flag to _load, which holds
it in a context variable while the value is deserialized, and
XComIterable.deserialize builds the iterable with it. The flag cannot go
through deserialize_value, whose signature XCom backends implement.
loop.py no longer needs to know about XComIterable.
LazyXComSequence.aget loaded through deserialize_value directly and so
skipped a backend's load_value; it now goes through XCom._load.
0 commit comments