[go-nuts] Re: Go modules replace statements referencing legacy codebases

2020-11-06 Thread Jim Minter
Sadly not. Doing this doesn't cause an error, but it also doesn't change the relevant replace directive in the go.mod file. Jim -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it,

Re: [go-nuts] strconv.ParseFloat panic

2020-11-06 Thread 'Dan Kortschak' via golang-nuts
OK, so you're not using Cgo, that leaves some other unsafe use, a data race or unlikely some weird compiler bug. I'd start looking in api.handleDPriceRange to see where the string input to strconv.ParseFloat is being constructed. On Fri, 2020-11-06 at 01:10 -0800, blade...@gmail.com wrote: > go

[go-nuts] Re: Go modules replace statements referencing legacy codebases

2020-11-06 Thread seank...@gmail.com
I think you should be able to do `go get ./... dep1@branchA dep2@branchB ...` On Friday, November 6, 2020 at 3:20:16 PM UTC+1 Jim Minter wrote: > Hi, > > Using Go 1.14, I'm working on a parent codebase which, in its go.mod > file, has a number of replace statements referencing legacy child >

[go-nuts] Go modules replace statements referencing legacy codebases

2020-11-06 Thread Jim Minter
Hi, Using Go 1.14, I'm working on a parent codebase which, in its go.mod file, has a number of replace statements referencing legacy child codebases which have not yet converted to Go modules. At this stage the legacy child codebases handle versioning by branch, rather than using semantic

Re: [go-nuts] strconv.ParseFloat panic

2020-11-06 Thread blade...@gmail.com
go version is 1.15 , cross compile on darwin and run on linux, i will try to run with race deector 在2020年11月6日星期五 UTC+8 下午4:34:21 写道: > The full panic would help, but somehow you have a string with a nil > pointer that is 4 bytes long. Where is the string generated? Are you > using Cgo?

Re: [go-nuts] strconv.ParseFloat panic

2020-11-06 Thread 'Dan Kortschak' via golang-nuts
The full panic would help, but somehow you have a string with a nil pointer that is 4 bytes long. Where is the string generated? Are you using Cgo? Have you run with the race detector? Also, what version of Go are you using? On Fri, 2020-11-06 at 00:00 -0800, blade...@gmail.com wrote: > i check

[go-nuts] Re: strconv.ParseFloat panic

2020-11-06 Thread Brian Candler
On Friday, 6 November 2020 08:00:32 UTC, blade...@gmail.com wrote: > > anyone can help me > You will need to give some basic info. At very least show the code that causes this crash, i.e. the code in external_api.go at line 330 with a few lines of context either side. Also say what version

[go-nuts] strconv.ParseFloat panic

2020-11-06 Thread blade...@gmail.com
i check my code, and strconv.ParseFloat(s, 64), s is a string, it is correct, but after run my program for a while, it's panic and report some output info. i cant't find why , anyone can help me output infor: panic: runtime error: invalid memory address or nil pointer dereference [signal