Inconsistent freezing

[zcasanova]

Is freeze broken or is there some magic behind it? My expectation is that if a component is frozen, when I run it directly or run something downstream from it, it would never actually execute. I am expecting it to use it's frozen outputs, but that is not happening. Well I mean, sometimes it does but sometimes it doesn't. I'm trying to figure out why it sometimes doesn't freeze, is it because I run it two times in a row? :-D, I can't figure it out. Broken or am I not understanding this?

Thank you.

[dosubot[bot]]

Hey @zcasanova! I'm here to assist you with any bugs, questions, or contributions. Let's tackle this together!

The freeze functionality is working as intended. When a component is frozen, it should use its frozen outputs instead of executing again. This behavior is verified by tests that show consistent outputs from frozen components, even when inputs change.

Here is a summary of how it works:

1. Initial Run Without Freezing: The component executes and generates an output.
2. Freezing the Component: The component is frozen, and its output is saved.
3. Subsequent Runs: When the component or downstream components are run again, the frozen component does not execute; it uses the saved output instead.

If you are experiencing inconsistent behavior, ensure that the component is correctly frozen and that the downstream components are not causing unexpected executions. The test script confirms that the freeze functionality prevents re-execution and uses the frozen outputs ^[1][2].

To continue talking to Dosu, mention @dosu.