Solved issue #40

[infopz]

Solved issue #40.
When two true entities were predicted as one, the classification differs based on the input list order

[ivyleavedtoadflax]

Thanks for this @infopz . Are you able to add a test for this please 🙏

[infopz]

Test added 👍

[ivyleavedtoadflax]

@infopz can you merge #71 into this, to see if it resolves the failing CI/CD please

[infopz]

Merged 👍

[davidsbatista]

Thanks for contributing - there's a failing issue but I will look into it.

[infopz]

Hi, can I do something to fix this?

[davidsbatista]

I'm planning to do it at the weekend., but if you want please, go ahead :)

[infopz]

It seems a permission problem on your side
remote: Permission to MantisAI/nervaluate.git denied to github-actions[bot].
but if this depends on something I can do, feel free to ask

[davidsbatista]

The PR LGTM, it's just the issue with the CI/CD now - @ivyleavedtoadflax do you have any idea what might be causing that?

[ivyleavedtoadflax]

I believe it is failing because the PR is originating from a fork which defaults to read access, but the coverage action needs write access to push to the repo.

/usr/bin/git push --force ***github.com/MantisAI/nervaluate.git github-pages-deploy-action/pcenusi52:coverage-badge
remote: Permission to MantisAI/nervaluate.git denied to github-actions[bot].
fatal: unable to access 'https://github.com/MantisAI/nervaluate.git/': The requested URL returned error: 403

I'll merge for now, and that will resolve it, but not sure the best way to resolve going forward.

[ivyleavedtoadflax]

Could also be that we can set the pages permission to write as here https://docs.github.com/en/actions/using-jobs/assigning-permissions-to-jobs#defining-access-for-the-github_token-scopes