Bug? - MeshRay gives False result with closed Mesh

oh grasshopper, it’s a love and hate situations at times

Please help me explain why one of my meshes results in a "NO’ hit with MeshRay when there should be one. I test it with 2 meshes, it occurs at both of them.
MeshRayHit.gh (127.4 KB)

I don’t know why, but by using a Remesh setting (Speed or Quality) gives full intersection with no missing rays

Hi inno, thanks for your suggestion. I noticed that as well after posting. But my ‘actual’ mesh is not included as it is generate on the fly, but i notice that sometimes this happens, as illustrated here with this example.

Maybe one of the guys at mcNeel can tell me if this is intended behahiour @Japhy , @stevebaer

seems to be related how mesh is constructed. For instance Mesh Sphere Ex gives all False’s, where as Brep Sphere converted to Mesh (setting Smooth), all True’s