Skip to content

fix: workflow incorrectly marked as completed while nodes are still executing#13

Open
tomerqodo wants to merge 4 commits intocodex_full_base_fix_workflow_incorrectly_marked_as_completed_while_nodes_are_still_executing_pr13from
codex_full_head_fix_workflow_incorrectly_marked_as_completed_while_nodes_are_still_executing_pr13
Open

fix: workflow incorrectly marked as completed while nodes are still executing#13
tomerqodo wants to merge 4 commits intocodex_full_base_fix_workflow_incorrectly_marked_as_completed_while_nodes_are_still_executing_pr13from
codex_full_head_fix_workflow_incorrectly_marked_as_completed_while_nodes_are_still_executing_pr13

Conversation

@tomerqodo
Copy link
Copy Markdown

Benchmark PR from agentic-review-benchmarks#13

Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: c7172e34ec

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment on lines 84 to +86
# Recursively propagate skip
self.propagate_skip_from_edge(edge.id)
self._state_manager.mark_edge_skipped(edge.id)
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Mark edge skipped before propagating skip

Calling propagate_skip_from_edge before mark_edge_skipped means the downstream node will still see the current edge as UNKNOWN, so analyze_edge_states returns has_unknown=True and the skip propagation stops. This leaves downstream nodes in UNKNOWN even when all their incoming edges should be skipped, which can stall traversal or prevent completion for graphs where the skipped node is the sole upstream. The previous ordering avoided this by marking the edge skipped before the recursive propagate.

Useful? React with 👍 / 👎.

Comment on lines +61 to +63
# Start execution and enqueue node
print(f"Starting execution for node: {downstream_node_id}")
self._state_manager.start_execution(downstream_node_id)
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Replace print with structured logging

This introduces a direct print() in backend code, which bypasses the logging subsystem (no log level, no context, and it can be dropped or spam stdout under workers). Repository rules require module-level logging instead of print, so this should use the existing logger pattern to ensure observability and consistent production behavior.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant