- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 36 for retracted$ (0.16 sec)
-
src/cmd/go/testdata/script/mod_retract_rationale.txt
stdout '^\[Ends with a BEL character. Beep!\x07\]$' # When there is a comment on a block, but not on individual retractions within # the block, the rationale should come from the block comment. go list -m -retracted -f '{{.Retracted}}' example.com/retract/rationale@v1.0.0-block stdout '^\[block comment\]$'
Registered: Wed Jun 12 16:32:35 UTC 2024 - Last Modified: Tue Sep 28 17:19:14 UTC 2021 - 3.2K bytes - Viewed (0) -
src/cmd/go/testdata/script/mod_list_retract.txt
! stdout . # 'go list -retracted pkg' shows retraction. go list -retracted -f '{{with .Module}}{{with .Retracted}}retracted{{end}}{{end}}' example.com/retract stdout retracted # 'go list -m' does not show retraction. go list -m -f '{{with .Retracted}}retracted{{end}}' example.com/retract ! stdout . # 'go list -m -retracted' shows retraction.
Registered: Wed Jun 12 16:32:35 UTC 2024 - Last Modified: Fri Aug 13 00:19:50 UTC 2021 - 4.8K bytes - Viewed (0) -
src/cmd/go/testdata/script/mod_get_retract.txt
# 'go get pkg@version' should update to a specific version, even if that # version is retracted. cp go.mod.orig go.mod go get example.com/retract@v1.0.0-bad stderr '^go: warning: example.com/retract@v1.0.0-bad: retracted by module author: bad$' go list -m example.com/retract stdout '^example.com/retract v1.0.0-bad$' # 'go get -u' should not downgrade from a retracted version when no higher # version is available. cp go.mod.orig go.mod
Registered: Wed Jun 12 16:32:35 UTC 2024 - Last Modified: Tue Sep 28 17:19:14 UTC 2021 - 2.1K bytes - Viewed (0) -
src/cmd/go/testdata/script/mod_retract_replace.txt
go mod edit -replace=example.com/retract/missingmod@v1.9.0=./missingmod-v1.9.0 go list -m -retracted -f '{{range .Retracted}}{{.}}{{end}}' example.com/retract/missingmod stdout '^bad version$' # If we replace the retracted version, we should not see a retraction. go mod edit -replace=example.com/retract/missingmod=./missingmod-v1.9.0 go list -m -retracted -f '{{if not .Retracted}}good version{{end}}' example.com/retract/missingmod stdout '^good version$'
Registered: Wed Jun 12 16:32:35 UTC 2024 - Last Modified: Tue Sep 28 17:19:14 UTC 2021 - 2K bytes - Viewed (0) -
src/cmd/go/testdata/script/mod_retract_rename.txt
# Populate go.sum. go get # 'go list -m -retracted' should load retractions, even if the version # containing retractions has a different module path. go list -m -retracted -f '{{with .Retracted}}retracted{{end}}' example.com/retract/rename # 'go list -m -u' should load retractions, too. go list -m -u -f '{{with .Retracted}}retracted{{end}}' example.com/retract/rename # 'go get' should warn about the retracted version. go get
Registered: Wed Jun 12 16:32:35 UTC 2024 - Last Modified: Tue Sep 28 17:19:14 UTC 2021 - 863 bytes - Viewed (0) -
src/cmd/go/internal/modload/build.go
// hide versions, since the "list" and "latest" endpoints are not // authenticated. return } else if errors.As(err, &retractErr) { if len(retractErr.Rationale) == 0 { m.Retracted = []string{"retracted by module author"} } else { m.Retracted = retractErr.Rationale } } else if m.Error == nil { m.Error = &modinfo.ModuleError{Err: err.Error()} } }
Registered: Wed Jun 12 16:32:35 UTC 2024 - Last Modified: Fri Feb 16 16:56:39 UTC 2024 - 13.3K bytes - Viewed (0) -
src/cmd/go/testdata/mod/example.com_retract_self_pseudo_v0.0.0-20200325131415-0123456789ab
See example.com_retract_self_pseudo_v1.9.0.txt. This version is not retracted. It should be returned by the proxy's @latest endpoint. It should match the @latest version query. TODO(golang.org/issue/24031): the proxy and proxy.golang.org both return the highest release version from the @latest endpoint, even if that version is retracted, so there is no way for the go command to discover an unretracted pseudo-version. -- .mod --
Registered: Wed Jun 12 16:32:35 UTC 2024 - Last Modified: Wed Aug 26 21:17:01 UTC 2020 - 568 bytes - Viewed (0) -
src/cmd/go/testdata/script/mod_retract_incompatible.txt
# +incompatible versions when looking for retractions. # Verifies #42601. go mod init m # Request a +incompatible version retracted in v1.0.0. go get example.com/retract/incompatible@v2.0.0+incompatible stderr '^go: warning: example.com/retract/incompatible@v2.0.0\+incompatible: retracted by module author$' # We should still see a warning if the +incompatible was previously in the # build list.
Registered: Wed Jun 12 16:32:35 UTC 2024 - Last Modified: Tue Sep 28 17:19:14 UTC 2021 - 716 bytes - Viewed (0) -
src/cmd/go/internal/list/list.go
The -retracted flag causes list to report information about retracted module versions. When -retracted is used with -f or -json, the Retracted field will be set to a string explaining why the version was retracted. The string is taken from comments on the retract directive in the module's go.mod file. When -retracted is used with -versions, retracted versions are listed together with unretracted versions. The -retracted flag may be used with or without -m.
Registered: Wed Jun 12 16:32:35 UTC 2024 - Last Modified: Fri Feb 16 16:56:39 UTC 2024 - 33.3K bytes - Viewed (0) -
src/cmd/go/internal/modinfo/info.go
GoMod string `json:",omitempty"` // path to go.mod file describing module, if any GoVersion string `json:",omitempty"` // go version used in module Retracted []string `json:",omitempty"` // retraction information, if any (with -retracted or -u) Deprecated string `json:",omitempty"` // deprecation message, if any (with -u) Error *ModuleError `json:",omitempty"` // error loading module
Registered: Wed Jun 12 16:32:35 UTC 2024 - Last Modified: Tue Mar 26 19:58:28 UTC 2024 - 3.1K bytes - Viewed (0)