New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gopkg.in/oleiade/lane.v1@v1.0.0: go.mod has non-....v1 module path "github.com/oleiade/lane" at revision v1.0.0 #1539
Comments
Hello, The lane dependency is used by the raft package. It's not easy for me to reproduce the problem, therefore I am just posing some ideas that might worth to test
making a
let me know what happens, you can point me to the specific commit of your project so I can try to reproduce the issue. |
Hello @baptiste-b-pegasys, |
do you have a link to the commit of the repo so I can take a look at it? |
Hello @baptiste-b-pegasys, I do not have a link. The error occurred during the go get phase, using the aforementioned go.mod. For convenience, I also paste it here: When I executed: |
frankly it is hard for me to help if I can't reproduce on my side.
|
Hello again @baptiste-b-pegasys , |
What is the latest GoQuorum package revision that I can download using go.mod ? |
The latest is v22.7.3 : https://github.com/ConsenSys/quorum/releases/tag/v22.7.3 and it is using gopkg.in/oleiade/lane.v1 v1.0.0 |
Yes, I'm having this issue as well, but I check https://github.com/oleiade/lane is not gopkg.in/oleiade/lane.v1 v1.0.0 How do I fix it @MisiakGeo |
Hello @YU-YUEHAO, I encountered a challenge in resolving this issue. Fortunately, I had a backup of the Go cache directory, allowing me to overcome the problem. I successfully proceeded by copying the old oleiade directory from the backup into the Go cache directory. |
Hello,
I am trying to use the goQuorum packages, and the following error regarding the oleiade/lane package appears
The go.mod that I am using is depicted in the following image:
Any directions that need to follow in order to be able to overcome this issue would be much appreciated.
The text was updated successfully, but these errors were encountered: