Skip to content

Conversation

@ABolouk
Copy link
Contributor

@ABolouk ABolouk commented Jan 5, 2026

Closes #452

Copy link
Collaborator

@LincolnPuzey LincolnPuzey left a comment

Choose a reason for hiding this comment

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

Thanks @ABolouk

Can you

  • Add yourself to the CONTRIBUTORS file.
  • Revert the changes to the pipeline class. Because a pipeline processes messages in order, I don't think there is any bug there.

@LincolnPuzey LincolnPuzey added this to the v2.0.1 milestone Jan 6, 2026
@LincolnPuzey LincolnPuzey changed the title debug: change logic of completed_count property for group and pipeline Bugfix: Change logic of completed_count property for group Jan 6, 2026
Add test for for when the jobs in a group finish out of order.
Copy link
Collaborator

@LincolnPuzey LincolnPuzey left a comment

Choose a reason for hiding this comment

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

Thanks again! I've added a regression test

@LincolnPuzey LincolnPuzey merged commit fcc04f5 into Bogdanp:master Jan 6, 2026
15 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.

group.completed_count does not actually returns the total number of jobs that have been completed

2 participants