Wei Hai ffdc23c6dd Make node-ordering heuristics defensive instead of blaming available[0] ... Addresses review feedback: the scheduler error path blamed available[0] even when picking failed while inspecting a later ready node, misreporting the node to the frontend. Instead of threading the node id through the exception, make is_output and is_async fully defensive. They are pure ordering heuristics, so a malformed node (a FUNCTION typo, or schema-derived attributes that raise) just means "not prioritized"; the node then runs through normal execution, where the error is reported against the correct node. The stage_node_execution try/except remains as a backstop only. Add a test for a node whose attribute access raises during the heuristics.		2026-06-26 15:41:11 -07:00
..
preview_method_override_test.py	feat(preview): add per-queue live preview method override (#11261)	2025-12-15 15:57:39 -08:00
scheduler_malformed_node_test.py	Make node-ordering heuristics defensive instead of blaming available[0]	2026-06-26 15:41:11 -07:00
test_cache_provider.py	Revert "Revert "feat: Add CacheProvider API for external distributed caching"" (#12915)	2026-03-12 21:17:50 -07:00
test_enrich_output.py	feat(assets): include asset id in executed WebSocket message (#13862)	2026-06-10 17:04:52 -07:00
validate_node_input_test.py	Reland union type (#5900)	2024-12-04 15:12:10 -05:00