# 'go get' should omit long messages.
go get example.com/retract/rationale@v1.0.0-long
stderr '^go: warning: example.com/retract/rationale@v1.0.0-long: retracted by module author: \(message omitted: too long\)'

# 'go list' should show the full message.
go list -m -retracted -f '{{.Retracted}}' example.com/retract/rationale
stdout '^\[lo{500}ng\]$'


# 'go get' should omit messages with unprintable characters.

! go test -json .

	# We should see only JSON output on stdout, no non-JSON.
	# To simplify the check, we just look for non-curly-braces, since
	# every JSON entry has them and they're unlikely to occur
	# in other error messages.
! stdout '^[^{]'
! stdout '[^}]\n$'

	# Since the only test we requested failed to build, we should
	# not see any "pass" actions in the JSON stream.
! stdout '\{.*"Action":"pass".*\}'

# and for changed explicit dependencies. 'go get' does not print messages
# for changed indirect dependencies.
go get rsc.io/sampler@none
stderr '^go: downgraded rsc.io/quote v1.5.2 => v1.3.0$'
stderr '^go: removed rsc.io/sampler v1.3.0$'
! stderr '^go get.*golang.org/x/text'
cmp go.mod go.mod.downgrade

# When removing or downgrading a requirement, 'go get' also prints a message

			t.Parallel()

			// Some basic log output to precede the failures.
			<-ready[i]
			t.Logf("this is sub-%d", i)
			ready[(i+1)%len(ready)] <- true

			// The actual failure messages we care about.
			<-ready[i]
			t.Errorf("error from sub-%d", i)
			ready[(i+1)%len(ready)] <- true
		})
	}

# This test checks error messages for non-existent packages in module mode.
# Veries golang.org/issue/35414
env GO111MODULE=on
cd $WORK

go list -e -f {{.Error}} .
stdout 'no Go files in '$WORK

go list -e -f {{.Error}} ./empty
stdout 'no Go files in '$WORK${/}'empty'

go list -e -f {{.Error}} ./exclude
stdout 'build constraints exclude all Go files in '$WORK${/}'exclude'

go list -e -f {{.Error}} ./missing

go build -mod=mod -o a5.exe ./usenewmodule
! stderr 'finding not-rsc.io/quote/v3'
grep 'not-rsc.io/quote/v3 v3.1.0' go.mod
exec ./a5.exe
stdout 'Concurrency is not parallelism.'

# Error messages for modules not found in replacements should
# indicate the replacement module.
cp go.mod.orig go.mod
go mod edit -replace=rsc.io/quote/v3=./local/rsc.io/quote/v3
! go get rsc.io/quote/v3/missing-package

cp go.mod go.mod.orig


# If a dependency cannot be resolved, 'go mod tidy' fails with an error message
# explaining the problem and does not update the go.mod file.
# TODO(bcmills): Ideally, with less redundancy than these error messages!

! go mod tidy

stderr '^go: example.com/untidy imports\n\texample.net/directnotfound: cannot find module providing package example.net/directnotfound: module example.net/directnotfound: reading http://.*: 404 Not Found$'

[short] skip
env GO111MODULE=on

# Download everything to avoid "finding" messages in stderr later.
cp go.mod.orig go.mod
go mod download
go mod download example.com@v1.0.0
go mod download example.com/badchain/a@v1.1.0
go mod download example.com/badchain/b@v1.1.0
go mod download example.com/badchain/c@v1.1.0

# Try to update example.com/badchain/a (and its dependencies).
! go get example.com/badchain/a
cmp stderr update-a-expected

stderr -count=2 '^go: finding module for package example\.net/y$'
stderr -count=2 '^go: finding module for package example\.net/z$'
stderr '^go: found example\.net/x in example\.net/x v0.1.0$'

	# TODO: These error messages should be clearer — it doesn't indicate why v0.2.0-pre is required.

handle auth

-- .access --
{
	"Username": "aladdin",
	"Password": "opensesame",
	"StatusCode": 404,