-LAN- a23c8fcb1a refactor: move execution limits from engine core to layer ... Remove max_execution_time and max_execution_steps from ExecutionContext and GraphEngine since these limits are now handled by ExecutionLimitsLayer. This follows the separation of concerns principle by keeping execution limits as a cross-cutting concern handled by layers rather than embedded in core engine components. Changes: - Remove max_execution_time and max_execution_steps from ExecutionContext - Remove these parameters from GraphEngine.__init__() - Remove max_execution_time from Dispatcher - Update workflow_entry.py to no longer pass these parameters - Update all tests to remove these parameters		2025-09-10 01:32:45 +08:00
..
__init__.py	Feat/loop node (#17273)	2025-04-02 13:53:26 +08:00
entities.py	feat: queue-based graph engine	2025-08-27 15:33:28 +08:00
loop_end_node.py	Merge remote-tracking branch 'origin/main' into feat/queue-based-graph-engine	2025-09-06 16:05:13 +08:00
loop_node.py	refactor: move execution limits from engine core to layer	2025-09-10 01:32:45 +08:00
loop_start_node.py	Merge remote-tracking branch 'origin/main' into feat/queue-based-graph-engine	2025-09-06 16:05:13 +08:00