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
Repo ystia/yorc used the old path to import gotestyourself indirectly.
This caused that github.com/gotestyourself/gotestyourself and gotest.tools coexist in this repo: https://github.com/ystia/yorc/blob/develop/go.mod (Line 52 & 118)
That’s because the gotestyourself has already renamed it’s import path from "github.com/gotestyourself/gotestyourself" to "gotest.tools". When you use the old path "github.com/gotestyourself/gotestyourself" to import the gotestyourself, will reintroduces gotestyourself through the import statements "import gotest.tools" in the go source file of gotestyourself.
"github.com/gotestyourself/gotestyourself" and "gotest.tools" are the same repos. This will work in isolation, bring about potential risks and problems.
In fact github.com/ory/dockertest recently fixes in its v3 the issue by now using gotest.tools/v3.
To properly fix this, Vault should be updated to use github.com/ory/dockertest/v3 and we should upgrade to a newer version of Vault (which is planned in #619).
Background
Repo
ystia/yorc
used the old path to importgotestyourself
indirectly.This caused that
github.com/gotestyourself/gotestyourself
andgotest.tools
coexist in this repo:https://github.com/ystia/yorc/blob/develop/go.mod (Line 52 & 118)
That’s because the
gotestyourself
has already renamed it’s import path from "github.com/gotestyourself/gotestyourself" to "gotest.tools". When you use the old path "github.com/gotestyourself/gotestyourself" to import thegotestyourself
, will reintroducesgotestyourself
through the import statements "import gotest.tools" in the go source file ofgotestyourself
.https://github.com/gotestyourself/gotest.tools/blob/v2.2.0/fs/example_test.go#L8
"github.com/gotestyourself/gotestyourself" and "gotest.tools" are the same repos. This will work in isolation, bring about potential risks and problems.
Solution
Add replace statement in the go.mod file:
Then clean the go.mod.
The text was updated successfully, but these errors were encountered: