From b4ae1cee4f9b90411c05a9140a17972f1859947b Mon Sep 17 00:00:00 2001 From: "rick.chan" Date: Thu, 2 Nov 2023 15:18:09 +0800 Subject: [PATCH] =?UTF-8?q?=E8=A1=A5=E5=85=85=20=E4=BD=BF=E7=94=A8=20Go=20?= =?UTF-8?q?=E5=8C=85=E7=9A=84=E5=B8=B8=E8=A7=81=E9=97=AE=E9=A2=98.?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: rick.chan --- .../Language/Go/Package/Go_包的创建和使用.md | 46 +++++++++++++++++++ 1 file changed, 46 insertions(+) diff --git a/Software/Development/Language/Go/Package/Go_包的创建和使用.md b/Software/Development/Language/Go/Package/Go_包的创建和使用.md index 674f8b6..23b2ac9 100644 --- a/Software/Development/Language/Go/Package/Go_包的创建和使用.md +++ b/Software/Development/Language/Go/Package/Go_包的创建和使用.md @@ -95,3 +95,49 @@ import ( ``` “\_”操作其实只是引入该包。当导入一个包时，它所有的 init() 函数就会被执行，但有些时候并非真的需要使用这些包，仅仅是希望它的 init() 函数被执行而已。这个时候就可以使用“\_”操作引用该包了。即使用“\_”操作引用包是无法通过包名来调用包中的导出函数，而是只是为了简单的调用其 init() 函数。 + +## 3. 使用 Go 包的常见问题 + +### 3.1. Why does go get fail with "invalid version: unknown revision"? + +#### 问 + +I published an update to a Go module, bumping the version to v1.1.0. I created a tag named v1.1.0 and pushed the tag to GitHub. + +https://github.com/depp/bytesize/releases/tag/v1.1.0 + +However, I cannot use this package in my other projects. I get an error that says, "invalid version: unknown revision v1.1.0". I don't know why the revision is "unknown", since it's tagged. + +```bash +$ go get github.com/depp/bytesize@v1.1.0 +go: downloading github.com/depp/bytesize v1.1.0 +go get github.com/depp/bytesize@v1.1.0: github.com/depp/bytesize@v1.1.0: verifying module: github.com/depp/bytesize@v1.1.0: reading https://sum.golang.org/lookup/github.com/depp/bytesize@v1.1.0: 410 Gone + server response: not found: github.com/depp/bytesize@v1.1.0: invalid version: unknown revision v1.1.0 +[Exit: 1] +``` + +#### 答 + +The tag was pushed after invoking go get once, which poisoned the Go module proxy cache. + +From : + + Note that if someone requested the version before the tag was pushed, it may take up to 30 minutes for the mirror's cache to expire and fresh data about the version to become available. + +The way to work around this before the cache expires is to use the GOPRIVATE environment variable to instruct go get to fetch this module directly, bypassing the cache. + +From : + + GOPRIVATE, GONOPROXY, GONOSUMDB + + Comma-separated list of glob patterns (in the syntax of Go's path.Match) of module path prefixes that should always be fetched directly or that should not be compared against the checksum database. + +The workaround is: + +```bash +$ GOPRIVATE=github.com/depp/bytesize go get github.com/depp/bytesize@v1.1.0 +``` + +Note that if you are already using GOPRIVATE, you will want to add modules rather than overriding the value completely. + +