Permalink
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
...
- 5 commits
- 3 files changed
- 1 contributor
Commits on Sep 6, 2023
-
Signed-off-by: Aleksa Sarai <[email protected]>
Commits on May 3, 2024
-
Signed-off-by: Aleksa Sarai <[email protected]>
-
join: don't allow .. and . in working path during resolution
The previous implementation would allow lexical components like ".." to be present in the intermediate path and wait for them to be cleaned at the very end. While this is technically okay to do (since we expand symlinks and the components are definitely purely lexical when we add them to the working path), it makes more sense to update the working path to equal the generated path (which is cleaned). This also reduces the possibility of a subtle bug here causing issues. Signed-off-by: Aleksa Sarai <[email protected]>
-
When returning an error, we should use the original path in the error message. Previously we would append the unresolved remaining path to the root, which is not a real path. Fixes: 322b993 ("Ditch pkg/errors, use native error (un)wrapping") Signed-off-by: Aleksa Sarai <[email protected]>
-
Signed-off-by: Aleksa Sarai <[email protected]>
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v0.2.4...v0.2.5