Update path module to vibe-core@2.8.5#2821
Conversation
|
✅ PR OK, no changes in deprecations or warnings Total deprecations: 0 Total warnings: 0 Build statistics: statistics (-before, +after)
-executable size=5063520 bin/dub
+executable size=5051680 bin/dub
rough build time=59sFull build output |
21620c6 to
5659959
Compare
7cd408a to
26558a8
Compare
That looks like fun. |
|
Ubuntu: ==> Missing normalization At a glance, they all look related to normalization. |
4bb5012 to
84c06c5
Compare
|
Only one test left failing: As well as some seemingly-unrelated vibe-core issue which vibe-d/vibe-core#421 might solve |
|
Needs more jpeg. I Can't read that at all. |
|
526b559 to
15a86fd
Compare
|
Running into a few issues here. Having the ability to differentiate Posix path from Windows path is great and all, but we need to provide a consistent serialization format for selection files. At the same time, we do want to accept Windows-only input. |
a20e052 to
33407aa
Compare
Currently our working directory is always the root, which means that we didn't care about absolute vs relative path.
On Windows, the root has a name, which is the drive, unlike on POSIX where the root is an empty name. This led to a flurry of problems because we assumed a POSIX style, where the FS is a directed graph, while on Windows it is multiple unconnected graphs (the drives cannot be accessed via a relative path).
3614094 to
911c500
Compare
|
Another one: vibe-d/vibe-inet#11 |
cd33956 to
81d7280
Compare
|
We're down to 1 oddly failing test on Windows, which I can't reproduce locally. |
The URL module actually includes a fix for an issue found while testing Dub.
|
@thewilsonator Would you mind approving ? |

No description provided.