You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
jayconrod opened this issue
Feb 24, 2020
· 0 comments
Labels
GoCommandcmd/gomodulesNeedsFixThe path to resolution is known, but the work has not been done.ToolsThis label describes issues relating to any tools in the x/tools repository.
Create a go.mod file with a replace directive with an unclean path on the right side. For example, the path might have a trailing slash, or a .. component in the middle.
Run any command that updates go.mod.
What did you expect to see?
The replace directive should be updated with a clean path.
go list -m -json should report the clean path.
If -mod=readonly is used, go list -m -json should still report the clean path, but go.mod should not be updated.
The text was updated successfully, but these errors were encountered:
jayconrod
added
NeedsFix
The path to resolution is known, but the work has not been done.
modules
Tools
This label describes issues relating to any tools in the x/tools repository.
labels
Feb 24, 2020
GoCommandcmd/gomodulesNeedsFixThe path to resolution is known, but the work has not been done.ToolsThis label describes issues relating to any tools in the x/tools repository.
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
Create a
go.mod
file with areplace
directive with an unclean path on the right side. For example, the path might have a trailing slash, or a..
component in the middle.Run any command that updates
go.mod
.What did you expect to see?
The
replace
directive should be updated with a clean path.go list -m -json
should report the clean path.If
-mod=readonly
is used,go list -m -json
should still report the clean path, butgo.mod
should not be updated.What did you see instead?
No change.
This partially caused #36193.
The text was updated successfully, but these errors were encountered: