Skip to content

Commit 2ccdba3

Browse files
sjrlanakin87
andauthored
fix: Remove old reno and update reno (#9357)
* Remove old reno and update reno * Update releasenotes/notes/dont-deepcopy-components-tools-b1be7ef7b4365116.yaml Co-authored-by: Stefano Fiorucci <[email protected]> --------- Co-authored-by: Stefano Fiorucci <[email protected]>
1 parent 6bef2c3 commit 2ccdba3

File tree

2 files changed

+4
-10
lines changed

2 files changed

+4
-10
lines changed
Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
enhancements:
33
- |
4-
Updated pipeline execution logic to use a new utility method `deepcopy_with_fallback`,
5-
which skips deep-copying of `Component`, `Tool`, and `Toolset` instances when used as
6-
runtime parameters. This prevents errors and unintended behavior caused by trying to
7-
deepcopy objects that contain non-copyable attributes (e.g. Jinja2 templates, clients).
4+
Updated pipeline execution logic to use a new utility method `_deepcopy_with_exceptions`, which attempts to deep copy an object and safely falls back to the original object if copying fails.
5+
Additionally `_deepcopy_with_exceptions` skips deep-copying of `Component`, `Tool`, and `Toolset` instances when used as runtime parameters.
6+
This prevents errors and unintended behavior caused by trying to deepcopy objects that contain non-copyable attributes (e.g. Jinja2 templates, clients).
7+
Previously, standard `deepcopy` was used on inputs and outputs which occasionally lead to errors since certain Python objects cannot be deepcopied.

releasenotes/notes/fix-deepcopy-in-pipeline-run-2b575c7b860f642f.yaml

Lines changed: 0 additions & 6 deletions
This file was deleted.

0 commit comments

Comments
 (0)