-
Notifications
You must be signed in to change notification settings - Fork 700
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
Cannot go get client #478
Comments
I have a similar issue using linux (ubuntu 18.04)
Removing Also with vgo (import was specified as
|
I think the issue now is with nats.go and stan.go libs not modified to change the nats-server |
Since you are doing a rename, may I ask why nats.go if it the trailing .go means having to end it with a /? I've never seen a go module do that, and it kinda ... smells. Why not name it nats-client or something more indicative of what it is? (maybe nats-go) Either way though, I am stuck which sucks because I was hoping to test nats today. :( |
@kozlovic, I think this is a good idea, i can test new tag as soon as possible. In the current situation build with 1.8.0 (latest) is still impossible with default configuration. UPD: I tried to change the imports in go tests in fork and it all worked (with nats.go, but i think stan.go fix must be similar) |
@coffeefedora About the naming, it is not my decision... |
Otherwise, projects pulling nats.go end-up with issues. Resovles #478 Signed-off-by: Ivan Kozlovic <[email protected]>
Issue with nats.go solved in 1.8.1, waiting for stan.go to perform a complete test. |
I think I need a nats-server v2.0.0-RC19 tag first (that will have the v2 requirement), then do the stan.go change. I wonder if that's enough or if I will have to have a nats-streaming-server change too... |
i cleared my go.sum and go.mod files, and tried adding again. It is trying to pull down v1.8.1 but no joy this is the error: get github.com/nats-io/nats.go/ |
@coffeefedora i working with go mod (vgo) and it works correctly, but |
@jar3b I need a v1.8.2 now because I just issued nats-server v2.0.0-RC19 that has proper go.mod with v2 requirements. If you build from docker (without any cache) then 1.8.1 will fail:
(the test app is importing |
As you see, 1.8.1 pulls RC8 that did not have go.mod modified for v2. |
But this is insane.. I really don't get how this thing works... (edit: nats.go's mod does not define the dependency to nats-server in the go.mod, and still it ends-up pulling rc8, why?) |
@jar3b I have deleted the old tag of nats-server that was But my guess is stan.go will be more complex because of nats-streaming-server using vendor with older gnatsd v1.4.1.. I can start with updating stan.go nats-server imports, but I believe that won't be enough. |
With test dockerfile
and go.mod
i got (20 min ago i got RC8, for now - RC19)
I hope it's all correct now (for nats.go) |
Yes, like I said, I deleted the old RC8 server tag that was being pulled as the latest. And it looks like nats.go works fine now. But I still get issues with sample app pulling streaming server/client... |
Yes, i can't
->
|
@jar3b that worked, thank you sir. But i saw a comment above that this is not the streaming client? both download links for nats and nats streaming go to the same github page... |
@coffeefedora yes this the core NATS client, could you share where you found those links? Thanks! |
I'm now running into this
|
@asim Are you having that on project that pulls stan.go? I am working on updating nats-streaming-server dependencies (nats-io/nats-streaming-server@dfa75d1). If from my stan.go repo I do |
I'm only making use of nats.go but I can't account for other things in the dependency graph that might rely on them. When I pin to the old version 1.7.2 everything is fine. |
All, did several repos updates, so would appreciate knowing if you guys still have issues. We have NATS Server that is still v2.0.0-RC19 and need to move to v2.0.0, which means that we will need NATS Streaming to issue v0.15.1 with updated dependency.
|
The replace statements do not actually fix the issue for me and the errors persist as
|
Hi @asim is it possible to get a link to the |
I believe I've resolved this. We were depending on another package which separately had stan dependencies. Please accept as resolved. |
Building a test app (with both stan.go and nats.go) was resolved today after
Thanks! |
Glad issue is resolved for all participants in this issue. Sorry again for the troubles. |
Filed in issue in |
Not that it matters, but this has effectively prevented me from using anything other than the new, and utterly horrible, "mod" concept in go. I, personally, hate this change and the massive amounts of my time that I will now have to waste managing go.mod replace blocks in every one of my projects that is now forced to use mod by way of using nats. |
@dcarbone there is also an archived version of the repository with the old name of the project that is not using modules in case it helps: https://github.com/nats-io/go-nats |
actually @wallyqs it was a litany of tangentially related issues that was the primary source of my anger this morning. so i apologize for displaying it here.
again, apologies. |
@dcarbone no worries, totally understand. glad to hear you could make it work with |
hi, i still getting error, please check below:
|
@yogihardi This is different. You are using go mod, so this is not going to be downloaded where you expect it to be if you were NOT using go mods. So do this instead and you should see it, along with the other nats-io deps that it may have pulled:
|
does not work with go mods
|
thanks @kozlovic |
@tegk You probably have some other dependencies that still refer to go-nats instead of nats.go. If you can't update those (or ask upstream repo to do so), I believe that you may be able to locally solve by having this statement in your go.mod:
(note I use the latest version, v1.9.1, although in your error message it looks like you/they were still using v1.8.1). |
Sirupsen |
@dan-compton Sorry but I am not sure what you mean by "Sirupsen". Did you mean to tag someone with that GitHub handle? If so, you did not (the @ is missing).. |
@kozlovic dude this issue still exists until now, why cant use solve it properly ? I still getting this error no matter what I do |
@bcba25 could you try with GOPROXY=direct? I think this might be solved in Go 1.14 too that is when modules became production ready |
@wallyqs alright will give it a try, thanks |
still seeing this issue when trying to do
|
getting the same error when using GOPROXY=direct |
Was able to solve the error after running |
@jextrevor thanks for sharing, looks there might still be some bugs in Go modules then... |
still seeing this error... |
What version of go do you use @jextrevor ? |
I'm using 1.13.1. I'm going to upgrade to 1.14.4 and see if the issue still exists there. |
Upgrading to 1.14.4 and to a newer version of the Go client would help with this issue (anything that matches version 1.8.1 would get this error as well). Reason seems to be that the Go proxy has cached a version during the rename that won't go stale, skipping the proxy is another work around this issue as well. |
I have a project that is outside of the go src folder, I am running go 1.12.5 on windows amd64 (win10) This is my first attempt to use NATS, not a great start!
Getting this error:
go get github.com/nats-io/nats.go/
go: finding github.com/nats-io/nats.go v1.8.0
go: finding github.com/nats-io/nkeys v0.0.2
go: finding github.com/nats-io/nuid v1.0.1
go: finding golang.org/x/crypto v0.0.0-20181203042331-505ab145d0a9
CreateFile github.com/nats-io/nats.go: The system cannot find the path specified.
The text was updated successfully, but these errors were encountered: