-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

..

fixtures/workflow

feat: queue-based graph engine

2025-08-27 15:33:28 +08:00

integration_tests

Revert "feat: email register refactor" (#25367)

2025-09-08 19:20:09 +08:00

test_containers_integration_tests

Merge remote-tracking branch 'origin/main' into feat/queue-based-graph-engine

2025-09-09 15:49:09 +08:00

unit_tests

refactor: move execution limits from engine core to layer

2025-09-10 01:32:45 +08:00

__init__.py

Initial commit

2023-05-15 08:51:32 +08:00