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.

首先使用 pygit2 1.2.0 重现已报告的 CI 流程：在非 bare repository 中修改并提交一个文件，使用 GIT_RESET_HARD 调用 repo.reset()，然后创建一个新的 Repository，并比较 repo.status() 与 repo.diff()。完成的标准是确定间歇性出现的 WT_MODIFIED 结果源自 pygit2 还是 libgit2，并记录原因或已确认的修复路径。