Bug: UV stretch instead of tiles, and shows misleading UV Editor results

This is pretty simple to reproduce. Create a new PB cube and stretch it a few meters in each direction.



Now connect the two near edges, and delete the resulting face:



Now select the far face (not shown), and extend the shape a few meters further:



Notice that the tiling of the near face is stretching now, instead of tiling at the top face is. Select the messed up face, and go into the UV editor for it. Interesting, it will show that everything's normal:



However, if you click "Convert to Manual" and then immediately click "Convert to Auto", it will now look like this:



So, two issues: The face gets messed up in the first place, and then the UV editor doesn't actually reflect it's incorrectness.

Reproduced in Unity 2018.3.7, with the following packages:

Spoiler: Packages

{
"dependencies": {
"com.unity.addressables": "0.5.3-preview",
"com.unity.ads": "2.0.8",
"com.unity.analytics": "3.2.2",
"com.unity.burst": "0.2.4-preview.50",
"com.unity.cinemachine": "2.2.8",
"com.unity.collab-proxy": "1.2.15",
"com.unity.collections": "0.0.9-preview.12",
"com.unity.jobs": "0.0.7-preview.6",
"com.unity.mathematics": "1.0.0-preview.1",
"com.unity.package-manager-ui": "2.0.3",
"com.unity.postprocessing": "2.1.4",
"com.unity.probuilder": "4.0.3",
"com.unity.progrids": "3.0.3-preview.4",
"com.unity.purchasing": "2.0.3",
"com.unity.render-pipelines.high-definition": "4.10.0-preview",
"com.unity.shadergraph": "4.10.0-preview",
"com.unity.textmeshpro": "1.3.0",
"com.unity.vectorgraphics": "1.0.0-preview.23",
"com.unity.modules.ai": "1.0.0",
"com.unity.modules.animation": "1.0.0",
"com.unity.modules.assetbundle": "1.0.0",
"com.unity.modules.audio": "1.0.0",
"com.unity.modules.cloth": "1.0.0",
"com.unity.modules.director": "1.0.0",
"com.unity.modules.imageconversion": "1.0.0",
"com.unity.modules.imgui": "1.0.0",
"com.unity.modules.jsonserialize": "1.0.0",
"com.unity.modules.particlesystem": "1.0.0",
"com.unity.modules.physics": "1.0.0",
"com.unity.modules.physics2d": "1.0.0",
"com.unity.modules.screencapture": "1.0.0",
"com.unity.modules.terrain": "1.0.0",
"com.unity.modules.terrainphysics": "1.0.0",
"com.unity.modules.tilemap": "1.0.0",
"com.unity.modules.ui": "1.0.0",
"com.unity.modules.uielements": "1.0.0",
"com.unity.modules.umbra": "1.0.0",
"com.unity.modules.unityanalytics": "1.0.0",
"com.unity.modules.unitywebrequest": "1.0.0",
"com.unity.modules.unitywebrequestassetbundle": "1.0.0",
"com.unity.modules.unitywebrequestaudio": "1.0.0",
"com.unity.modules.unitywebrequesttexture": "1.0.0",
"com.unity.modules.unitywebrequestwww": "1.0.0",
"com.unity.modules.vehicles": "1.0.0",
"com.unity.modules.video": "1.0.0",
"com.unity.modules.vr": "1.0.0",
"com.unity.modules.wind": "1.0.0",
"com.unity.modules.xr": "1.0.0"
}
}

 

Just got around to updating to 4.0.4, and I wanted to confirm that this issue appears to be fixed. Thanks again.