Comment 2 for bug 1828119

My apologizes, I didn't see this response earlier.

I have just tested with:
  * Version: (5.1.0-rc2-24-gdb31b7902)
  * Version: (5.1.0-1305-gc84c10fa0)
both with python 3. Full version info tested is attached.

I can confirm that I do *not* see this bug with either of these versions and can't replicate.

However, the original bug I reported was with a 6.0 pre-release (r15606) which I was testing back then and no longer have access to.

If you could point me to the equivalent 6.0 branch for testing I would be happy to build it and test again. I am confused about the branches and version numbering.

Just speculating here, but my hunch is that this is probably something to do with detecting if a shape is open or closed or something similar; perhaps failing on some exact case with exactly equal successive coordinates in one dimension. If that is the case, then would that be something handled by OpenCascade? I notice that the OpenCascade version has bumped up a lot (6.9.1 -> 7.3.0) between the build I saw the bug with and now. So perhaps they have fixed it.