go.dev: allow force |
您所在的位置:网站首页 › 调查问卷分析表格 › go.dev: allow force |
Can you say what triggered that reindexing? My guess is that someone made a request to proxy.golang.org/github.com/aaronsky/asc-go/@latest, either by visiting the URL directly or by using the Go command. proxy.golang.org and https://golang.org/cmd/go/#hdr-Module_downloading_and_verification have more information on this topic. We monitor https://index.golang.org/index regularly for new modules to add to pkg.go.dev. See our design doc. GoDoc has already updated to reflect the new documentation, but I have been struggling to get pkg.go.dev to update. Based on my searches this seems like a fairly common issue with pkg.go.dev. In general, are you looking for the latest version (i.e. the version returned by https://proxy.golang.org/github.com/aaronsky/asc-go/@latest), or the master version (i.e. https://proxy.golang.org/github.com/aaronsky/asc-go/@v/master.info)? Pkg.go.dev supports both (see #36811 and #37002 for details). When you make a request to https://pkg.go.dev/github.com/aaronsky/asc-go@master, we will automatically refetch and refresh the master version, when that request is made. If a refresh button is out of the question due to technical concerns, more guidance on how often the package index is updated and how to affect that index as a package author would be helpful. If the above doesn't answer your question, or you have suggestions for better documentation or addressing a specific use case, let me know. |
今日新闻 |
推荐新闻 |
CopyRight 2018-2019 办公设备维修网 版权所有 豫ICP备15022753号-3 |