@mdomke this is my first contribution to the project, I wonder if there is a utility that ignores the order for things such as $sort, in this case the order if relevant for the count, but in the case where count is equal, the order becomes irrelevant, I don't know if there is some helper function that considers this.

Please do let me know, I am happy to add anything that you see necessary help the feature become supported.

I have updated and tested but haven't been able to get rid of the assertion error from the diff that states that it is in the incorrect order.

E               AssertionError: Unexpected Diff:
E                       fake.0.pipeline_b.0._id != real.0.pipeline_b.0._id (1 != 2)
E                       fake.0.pipeline_b.1._id != real.0.pipeline_b.1._id (2 != 4)
E                       fake.0.pipeline_b.2._id != real.0.pipeline_b.2._id (4 != 1)

Here is what the return looks like:

[{'_id': 1, 'count': 2}, {'_id': 2, 'count': 2}, {'_id': 4, 'count': 2}, {'_id': 3, 'count': 1}]

Since all of them have a count of 2, technically speaking (or at least up to my knowledge) they could come back from mongodb in any order.

I am not sure if there is a way around this. @mdomke How would you approach it?

Can you maybe rebase your changes on the current development version, so that we actually have a test-pipeline where I could look at the error? The tip of the develop-branch uses GitHub Actions.

Sure, let me do that.

@mdomke I just rebased against the latest develop branch. Please let me know if there is anything else I should do.