Try /wsl_root/src/ansible/ (with a trailing slash)?

that worked. there's no indication in the UI that the trailing slash is required, the link rendered works fine

also, I would not expect it to fail in this direction... if I added a slash there and it wasn't necessary, I can see it failing due to double-slashing, but as it is (and with the expectation that "everything below is covered"), I would expect it to work either way

in my opinion, either the feature needs to be resilient and work with or without a trailing slash, or verify the path exists and is a file (I'm guessing this is the case for no slash?) otherwise raise a visual warning that it's misconfigured

I ran into an identical issue (and debugged on chat). Agreed that there could be better messaging around this.

Yeah, current behavior is garbage. Not sure if I changed it by accident while doing other changes or we just didn't run into it before, but there's no technical or product reason for it to work like it currently does.

We have a somewhat-legitimate technical reason for this behavior: when we compute which-packages-own(list-of-paths), we do so by splitting the paths into components and then querying for the components. a/b/ is the best database representation for this.

We could normalize everything to this form, which would be good from a technical point of view, but would mean that you'd type a/important.c and we'd store and display a/important.c/, which would have the same effect but likely be confusing.

Probably better is to add pathIndex, store hash(normal(path)) there, normalize everything to /a/important.c/ form internally, and keep path as the human-readable display value, but this involves some migrations and work and needs to touch a few things.

I don't think this behavior changed, it appears to be present when Owners came out of Facebook in rP23f882a0, circa 2011.

Probably better is to add pathIndex

Specifically, the issue here is that paths may be arbitrarily long but path is currently a text255, so Owners can't actually interact with path rules that apply to paths with more than 255 characters today. Fortunately, these have yet to crop up in the wild, I think.

I'm going to make these changes:

• Add pathIndex, a new hash digest column.
• Begin populating pathIndex when OwnersPath records are saved.
• Migrate the OwnersPath table to store a digest of path in pathIndex.
• Migrate the OwnersPath table to remove rows with a duplicate <packageID, repositoryPHID, pathIndex> tuple. This is not currently enforced at the database level.
• Add a unique key to <packageID, repositoryPHID, pathIndex>.
• Modify path to LONGTEXT. Ideally, this should be LONGBLOB because paths may not be UTF8, but I'm comfortable saying that the Owners tool can not interact with non-UTF8 path rules for the forseeable future.
• Add pathDisplay.
• Begin populating pathDisplay when OwnersPath records are saved.
• Migrate the OwnersPath table to set pathDisplay = path.
• Add code to normalize path on save.
• Show the user pathDisplay in the UI.

Also T12590 is pretty egregious and should really get fixed. I think we have the technology nowadays.