Re: [go-nuts] a way to query the module sum of a dependency with the go tool?

2019-03-22 Thread Dan Kortschak
*bump* On Fri, 2019-03-22 at 08:33 +1030, Dan Kortschak wrote: > Is there a command that does something like `go list -m ` but > also outputs the sum for the module and module's go.mod? Other than > `grep go.sum`. > > thanks > Dan > -- You received this message because you are subscribed to t

Re: [go-nuts] Re: Accessing *[]uint64 from assembly - strange memory corruption under heavy load - any ideas?

2019-03-22 Thread 'Keith Randall' via golang-nuts
Your assembly looks ok to me. At least, the sections you've shown us. It would help if we could see all of it and/or the whole program. You might want to try putting a len>0 test in the pop and a len > On Fri, Mar 22, 2019 at 10:55 AM Robert Johnstone > > wrote: > > > > I don't see any memory

[go-nuts] time.Now.UnixNano() incorrect under windows7?

2019-03-22 Thread Slawomir Pryczek
Hi Guys, so i have this small go program which works fine under linux... but there's some very strange issue with getting microsecond-precision time under windows7. https://play.golang.org/p/N9F7xpx7hEr It won't run properly under playground so let me just paste here so you can see the behavi

Re: [go-nuts] what +build flags do I need to distinguish between ios and macos please?

2019-03-22 Thread Ian Lance Taylor
On Fri, Mar 22, 2019 at 5:04 PM whitehexagon via golang-nuts wrote: > > I'm experimenting with some cross platform development in Go. btw loving the > WASM support! > > so for mac desktop I'm using // +build darwin,386 > for android I can see a GOOS android value, so I'm guessing +build > andro

Re: [go-nuts] Re: Accessing *[]uint64 from assembly - strange memory corruption under heavy load - any ideas?

2019-03-22 Thread Ian Lance Taylor
On Fri, Mar 22, 2019 at 10:55 AM Robert Johnstone wrote: > > I don't see any memory barriers in your assembly. If you are modifying the > backing array while it is being scanned by the GC, there could be some > interaction. I don't know enough about the GC internals to say more than > that.

[go-nuts] Re: Accessing *[]uint64 from assembly - strange memory corruption under heavy load - any ideas?

2019-03-22 Thread Robert Johnstone
I don't see any memory barriers in your assembly. If you are modifying the backing array while it is being scanned by the GC, there could be some interaction. I don't know enough about the GC internals to say more than that. If you look at when memory barriers are inserted by the Go compiler,

Re: [go-nuts] How to lower listen backlog for tcp socket

2019-03-22 Thread Janne Snabb
I think you can't. The listen backlog is set to whatever is kernel's maximum backlog value. See for example /usr/local/go/src/net/sock_linux.go to see how that is determined. There has been a bug report about it: https://github.com/golang/go/issues/6079 I think it has been incorrectly clos

Re: [go-nuts] How to lower listen backlog for tcp socket

2019-03-22 Thread Agniva De Sarker
Oh I see. Then this is a linux networking question rather than a Go question. I know there are sysctl settings for that. But offhand, I am not aware of the code for it using socket options. On Friday, 22 March 2019 22:19:26 UTC+5:30, Peter Wang wrote: > > I know Control func and syscall.Setsocko

Re: [go-nuts] How to lower listen backlog for tcp socket

2019-03-22 Thread Shulhan
On Thu, 21 Mar 2019 23:18:34 +0800 Wangbo wrote: > I try to use net.ListenConfig, but fail > can someone give example ? > What do you mean by fail? What have you try? Have you tried using syscall.Listen [1] ? [1] https://golang.org/pkg/syscall/#Listen -- { "github":"github.com/shuLhan", "s

Re: [go-nuts] How to lower listen backlog for tcp socket

2019-03-22 Thread Wangbo
I know Control func and syscall.SetsockoptInt(fd, syscall.AF_INET, syscall.SO_REUSEADDR, 1) cat set reuseadd But how to adjust listen backlog since i never find socket options for it. Agniva De Sarker 于2019年3月22日周五 下午4:44写道: > Using ListenConfig is the way to go. > > The Control func is passed

Re: [go-nuts] Accessing *[]uint64 from assembly - strange memory corruption under heavy load - any ideas?

2019-03-22 Thread jsonp via golang-nuts
I'm not making any function calls in the assembly, just writing to memory addresses that represent the elements / len of the slice. I've also tried using LockOSThread() to see if that made any difference, alas it does not. On Friday, March 22, 2019 at 4:59:30 AM UTC-7, Robert Engels wrote: > > A

Re: [go-nuts] Accessing *[]uint64 from assembly - strange memory corruption under heavy load - any ideas?

2019-03-22 Thread jsonp via golang-nuts
The assembly should never write to a position / update the len beyond the backing array (specifically, the assembly is generated from code where the 'max stack depth' has been computed and validated, and the capacity of the slice is that size). On Friday, March 22, 2019 at 5:39:36 AM UTC-7, How

[go-nuts] Re: Have Any One Experience With Print CSS Modules Using in Golang

2019-03-22 Thread howardcshaw
That is just a wrapper for wkhtmltopdf - I'd suggest looking into that library and tool https://wkhtmltopdf.org/ first. If you can get the wkhtmltopdf command line tool to convert your file happily, then getting the Go wrapper to do the same is probably possible. But if the command line tool ca

Re: [go-nuts] Accessing *[]uint64 from assembly - strange memory corruption under heavy load - any ideas?

2019-03-22 Thread howardcshaw
On Friday, March 22, 2019 at 12:27:37 AM UTC-5, Tom wrote: > > The allocation is in go, and assembly never modifies the size of the > backing array. Assembly only ever modifies len, which is the len of the > slice and not the backing array. > > Can the assembly ever modify len to a size greater t

Re: [go-nuts] Accessing *[]uint64 from assembly - strange memory corruption under heavy load - any ideas?

2019-03-22 Thread Robert Engels
Are you making any calls modifying the len that would allow GC to occur, or change stack size? You might need to pin the Go routine so that the operation you are performing is “atomic” with respect to those. This also sounds very scary if the Go runtime every had a compacting collector. > On

Re: [go-nuts] boringcrypto+fipsonly: way more strict than fips 140-2?

2019-03-22 Thread Wojciech S. Czarnecki
On Thu, 21 Mar 2019 16:57:14 -0700 (PDT) Eric Grosse wrote: I apologize for being too terse. I in no way meant to undermine the FIPS procedure's value as a remedy to the real problem of knowing what code (and/or hardware) runs in security sensitive environments. Just stated the obvious, that for

Re: [go-nuts] How to lower listen backlog for tcp socket

2019-03-22 Thread Agniva De Sarker
Using ListenConfig is the way to go. The Control func is passed the raw socket connection on which you can apply whatever socket options you choose. You have to go through 2 layers to get to the fd. ListenConfig{ Control: func(conn syscall.RawConn) error { return conn.Control(func(fd uintp

[go-nuts] [ANN] rescached: resolver (DNS) cache daemon

2019-03-22 Thread Shulhan
rescached is a daemon that caching internet name and address on local memory for speeding up DNS resolution. rescached primary goal is only to caching DNS queries and answers, used by personal or small group of users, to minimize unneeded traffic to outside network. This release is dedicated to A

[go-nuts] Re: Do I need to use runtime.KeepAlive in this case?

2019-03-22 Thread Cholerae Hu
I've found this issue https://github.com/golang/go/issues/10303 which can answer my questions. 在 2019年3月21日星期四 UTC+8下午1:56:17,Cholerae Hu写道: > > package main > > // void a(long *p) {} > import "C" > > import ( > "unsafe" > ) > > //go:noinline > func b() { > x := int64(0) > C.a((*C.long)(unsafe.Po