flaky repo.reset() behavior

This issue is about repo.reset() not seeming to work reliably 100% of the time.

I have some CI tests that modify a file in a non-bare repo, commit the change to a branch, and then call repo.reset() with GIT_RESET_HARD to restore to a different commit. After calling reset, to confirm that the reset was successful, the test creates a new Repository object and checks the repository's status using repo.status(). Occasionally (but very rarely), the status check comes back showing the original file still as WT_MODIFIED. A subsequent call to repo.diff() confirms the difference in the file. Is there something pygit2 is or isn't doing that could cause reset() to behave flakily like this? Or is libgit2 the more likely culprit?

This is using pygit2 1.2.0. I can try upgrading, but is there a reason to think this would be fixed in a newer version (e.g. a known issue that was fixed)? I haven't found anything like this in pygit2 or libgit2's issue tracker or release notes.

Empieza reproduciendo la secuencia de CI reportada con pygit2 1.2.0: modifica y haz commit de un archivo en un repositorio no bare, llama a repo.reset() con GIT_RESET_HARD, crea después un nuevo Repository y compara repo.status() con repo.diff(). El trabajo estará terminado cuando se haya identificado si el resultado intermitente WT_MODIFIED procede de pygit2 o de libgit2 y se haya documentado la causa o una vía de solución confirmada.