Skip to content

BUG - EvaluateRetrieval's evaluate doesn't consider results dict order #184

Description

@vd-omermazig

I'm guessing it because it runs C code underneath, and in the translation to HashMap the iteration order because the lexical order of the keys instead of the original order of the dict.

I opened a pull request that fixes the issue:

#183

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions