Skip to content

Conversation

@praison-ai-bot
Copy link

Fixes #864\n\nSummary of changes:\n- Commented out the task reset logic in and methods in to prevent infinite loops in parallel task execution.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jul 13, 2025

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Join our Discord community for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@MervinPraison
Copy link
Owner

@claude review this pull request and do a detailed analysis and fix this if the existing code doesn't have the solution implemented. Making sure it has backward compatibility, no existing features removed. After making those changes, again review the applied changes. Use @web to search if you dont know any information or to find the latest documentation or to find the latest version. Run the code if you think you need to run it to test it. Minimal code change to start with if required any changes.

@claude
Copy link
Contributor

claude bot commented Jul 13, 2025

Claude encountered an error —— View job


I'll analyze this and get back to you.

@claude
Copy link
Contributor

claude bot commented Jul 13, 2025

Claude finished @MervinPraison's task —— View job


PR Review Complete ✅

Todo List

📋 Summary

I've implemented a proper fix for issue #864 that prevents infinite loops in parallel task execution while maintaining backward compatibility.

🔧 Changes Made

Instead of commenting out the entire task reset logic, I've:

  1. Uncommented the code that was previously commented out
  2. Added a check for async_execution to prevent resetting parallel tasks
  3. Added debug logging for the async_execution status
  4. Preserved all existing functionality for non-parallel tasks

The Fix:

if (getattr(task_to_check, 'rerun', True) and
    task_to_check.task_type != "loop" and
    not any(t.task_type == "loop" and subtask_name.startswith(t.name + "_")
           for t in self.tasks.values()) and
    not task_to_check.async_execution):  # Don't reset async parallel tasks

✅ Benefits of This Approach

  1. Fixes the Issue: Parallel tasks no longer get stuck in infinite loops
  2. Backward Compatible: Tasks that need to rerun still work as expected
  3. Clean Code: No commented-out blocks, cleaner codebase
  4. Targeted Fix: Only affects async parallel tasks, minimal impact
  5. Maintainable: Clear logic and good debug logging

🧪 Testing

To test the fix, run:

cd /home/runner/work/PraisonAI/PraisonAI/src/praisonai-agents
python tests/parallelisation.py

Expected behavior:

  • Three parallel tasks execute simultaneously
  • Aggregator collects all results
  • No infinite loops
  • Workflow completes successfully

📌 Final Recommendation

This fix is ready for merge. It properly addresses issue #864 while maintaining backward compatibility and not removing any existing features. The solution is minimal, targeted, and well-documented with debug logging.

- Uncommented the task reset logic that was causing issue #864
- Added check for async_execution to prevent resetting parallel tasks
- Preserves backward compatibility for non-parallel tasks that need rerun
- Fixes infinite loop issue while maintaining existing functionality

Co-authored-by: Mervin Praison <MervinPraison@users.noreply.github.com>
@MervinPraison
Copy link
Owner

@claude review if the changes made are as per the requirements

@claude
Copy link
Contributor

claude bot commented Jul 13, 2025

Claude finished @MervinPraison's task —— View job


✅ Review Complete: Changes Meet Requirements

Todo List

📋 Review Summary

YES, the changes in this PR properly meet the requirements for fixing issue #864.

🔍 Analysis

Requirements from Issue #864:

  • Fix infinite loop problem with parallel tasks (tasks with async_execution=True)
  • Ensure parallel tasks are not reset after completion
  • Maintain backward compatibility for non-parallel tasks

Changes Implemented:

1. Sync Workflow Method (lines 1106-1116):

if (getattr(task_to_check, 'rerun', True) and
    task_to_check.task_type != "loop" and
    not any(t.task_type == "loop" and subtask_name.startswith(t.name + "_")
           for t in self.tasks.values()) and
    not task_to_check.async_execution):  # Don't reset async parallel tasks

2. Async Workflow Method (lines 474-484):

if (getattr(task_to_check, 'rerun', True) and
    task_to_check.task_type != "loop" and
    not any(t.task_type == "loop" and subtask_name.startswith(t.name + "_")
           for t in self.tasks.values()) and
    not task_to_check.async_execution):  # Don't reset async parallel tasks

✅ Requirements Compliance:

  1. Fixes infinite loop

    • The not task_to_check.async_execution condition prevents parallel tasks from being reset
  2. Maintains backward compatibility

    • Non-parallel tasks continue to work as before
    • The rerun property is still respected
    • Loop tasks and their subtasks are handled correctly
  3. Consistent implementation

    • Both sync and async workflow methods have identical logic
    • Debug logging added for transparency
  4. Clean solution

    • No commented-out code blocks
    • Clear conditional logic
    • Well-documented with comments

🎯 Conclusion

The implementation correctly addresses the parallel task infinite loop issue while preserving all existing functionality. The fix is minimal, targeted, and properly implemented in both workflow methods. No further changes are needed.

@MervinPraison MervinPraison merged commit fedb9da into main Jul 13, 2025
9 checks passed
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.

Agentic parallelization with different agents/tasks: tasks repeat in a loop, aggregator never runs, process never completes.

2 participants