Re: [go-nuts] Virus detection issues on Windows/386 binaries built with -ldflags -s -w

VT detected issues. As mentioned these are false positives: https://www.virustotal.com/gui/file/77cbc92defdabf7e308849f0dd5e784010d9b4548b99b50df52533b949a14d85/detection On Tuesday, February 11, 2020 at 11:50:37 PM UTC-5, ajstarks wrote: > > A bit more info: building natively on Windows 10,

Re: [go-nuts] Go without garbage collector

I found a more recent academic paper that proves my conclusions: https://www.researchgate.net/publication/326369017_From_Manual_Memory_Management_to_Garbage_Collection I am sure you can

Re: [go-nuts] Go without garbage collector

Here is a paper from 2005 https://people.cs.umass.edu/~emery/pubs/gcvsmalloc.pdf that proves otherwise. GC techniques have radically improved since then, some with hardware support, so much so that it is no longer a contest. To

Re: [go-nuts] Virus detection issues on Windows/386 binaries built with -ldflags -s -w

A bit more info: building natively on Windows 10, the detection is NOT triggered. I will submit the offending file. On Tuesday, February 11, 2020 at 11:30:48 PM UTC-5, andrey mirtchovski wrote: > > you can find similar detections on virustotal. unfortunately it looks > like a false positive:

Re: [go-nuts] Go without garbage collector

Actually, it was not proven. And in practice manual memory management seems to be outperforming GC in majority of cases. On Tuesday, February 11, 2020 at 5:59:26 PM UTC-8, robert engels wrote: > > It’s been PROVEN that GC outperforms all manual memory management except > in EXTREMELY isolated

Re: [go-nuts] Virus detection issues on Windows/386 binaries built with -ldflags -s -w

sorry, wanted to add: submit your file to VT and see if it triggers a detection there (like in my link it is most likely that only the MS engine will detect it). then you have a case to argue. On Tue, Feb 11, 2020 at 9:29 PM andrey mirtchovski wrote: > > you can find similar detections on

Re: [go-nuts] Virus detection issues on Windows/386 binaries built with -ldflags -s -w

you can find similar detections on virustotal. unfortunately it looks like a false positive: https://www.virustotal.com/gui/file/93eb448cedd4b4355065a4f9193d8548b02bc56ed5ba9e774095f9ab3da46227/detection there are members of this community working for microsoft, perhaps they'll have an avenue

[go-nuts] Virus detection issues on Windows/386 binaries built with -ldflags -s -w

When building Windows binaries for pdfdeck [1] ( https://github.com/ajstarks/deck/tree/master/cmd/pdfdeck) I noticed that the binary generated with on linux with: GOOS=windows GOARCH=386 go build -ldflags="-s -w" -o windows-386-pdfdeck.exe github.com/ajstarks/deck/cmd/pdfdeck will cause the

Re: [go-nuts] Re: Checking if two map variables refer to the same map

On Tue, Feb 11, 2020 at 3:55 PM 'Kevin Regan' via golang-nuts wrote: > > Would something like this work: > > m1 := make(map[string]string) > m2 := m1 > > if == { >... > } That would do something but it's not a particularly interesting property. I'm not sure what you are trying to check.

Re: [go-nuts] reflect.StructOf embedded base type with pointer type method set

Well, I didn't point out the problem succinctly. And it's easy to work around the problem by making the field a pointer. And the compiler does it correctly otherwise someone else would have reported or fixed it already. Sorry the compiler and standard library are creating so much work. It's

Re: [go-nuts] Re: Checking if two map variables refer to the same map

On Tue, Feb 11, 2020 at 5:51 AM roger peppe wrote: > > I believe that the main reason that equality isn't defined on maps (and > slices) is to preserve the future possibility that equality might work at a > whole-value level rather than on a reference level. I suspect that one of > these days

[go-nuts] arm64 builder on raspberry pi 3B/3B+

I have been wanting an arm64 builder to do local testing for Gonum recently. Unfortunately, though RPi 3 and 4 have 64 bit cores, Raspbian is 32 bit, so they don't satisfy. However, I found this article[1] which goes through installing a UEFI bootloader and vanilla Debian Buster install on

Re: [go-nuts] Help with Oauth2 "grant_type=client_credentials"

This looks like what I need. Thanks Chris. On Tuesday, February 11, 2020 at 7:45:56 PM UTC-5, Chris Broadfoot wrote: > > Try this package: > https://pkg.go.dev/golang.org/x/oauth2/clientcredentials?tab=doc > > On Tue, Feb 11, 2020, 4:43 PM andrey mirtchovski > wrote: > >> i would strongly

Re: [go-nuts] Go without garbage collector

It’s been PROVEN that GC outperforms all manual memory management except in EXTREMELY isolated cases (very non-traditional allocation or deallocation patterns). It’s all about constraints and tolerances. You design a “system” that takes both into account - if not, you’re not engineering,

Re: [go-nuts] Help with Oauth2 "grant_type=client_credentials"

Try this package: https://pkg.go.dev/golang.org/x/oauth2/clientcredentials?tab=doc On Tue, Feb 11, 2020, 4:43 PM andrey mirtchovski wrote: > i would strongly advise against implementing advice received online > for something as important as auth. my suggestion is to work with curl > from the

Re: [go-nuts] Help with Oauth2 "grant_type=client_credentials"

i would strongly advise against implementing advice received online for something as important as auth. my suggestion is to work with curl from the command line (examples are given on the webpage you linked) until you have the process working. implementing that afterwards using http.Client will be

[go-nuts] Help with Oauth2 "grant_type=client_credentials"

Hi, I'm not a programmer. I have this working in PowerShell. Requirement: Query hardware vendor web APIs, using the device serial number, for device warranty status. The vendors require that the "client_id" and "client_secret", as well as the "grant_type=client_credentials" be

Re: [go-nuts] Re: Checking if two map variables refer to the same map

Would something like this work: m1 := make(map[string]string) m2 := m1 if == { ... } On Tue, Feb 11, 2020 at 5:50 AM roger peppe wrote: > I believe that the main reason that equality isn't defined on maps (and > slices) is to preserve the future possibility that equality might work at a

Re: [go-nuts] Go without garbage collector

What about #vlang ? https://vlang.io/ On Sunday, 17 June 2012 22:40:30 UTC+2, nsf wrote: > > On Sun, 17 Jun 2012 11:48:53 -0700 (PDT) > ⚛ <0xe2.0...@gmail.com > wrote: > > > > You can't have Go syntax without a garbage collector. > > > > > > > I wouldn't be so sure about it. > > > > Let

[go-nuts] x/net/trace: a race to the Finish()

I use the x/net/trace package to trace requests, and I am running into a panic caused by adding to a trace after it was Finished[1]. Here's the scenario: - One incoming request leads to 2 parallel requests to backends. - We return the fastest backend's response to the user and Finish the

[go-nuts] Delve v1.4.0 released!

Hey Gophers, We've just released Delve v1.4.0 including new features, fixes and more! Check out the CHANGELOG for more details: https://github.com/go-delve/delve/blob/master/CHANGELOG.md#140-2019-02-11. Thanks to everyone who contributed during this release cycle! -- You received this

Re: [go-nuts] Re: Checking if two map variables refer to the same map

I believe that the main reason that equality isn't defined on maps (and slices) is to preserve the future possibility that equality might work at a whole-value level rather than on a reference level. I suspect that one of these days a final decision will be made... On Mon, 10 Feb 2020 at 23:42,

Re: [go-nuts] Re: solving: panic: reflect.Value.Interface: cannot return value obtained from unexported field or method

On Tue, 11 Feb 2020 at 03:38, Ian Lance Taylor wrote: > On Mon, Feb 10, 2020 at 4:15 AM 'Axel Wagner' via golang-nuts > wrote: > > > > It's reflect, so I don't feel confident in making any absolute > statements (we've talked about it a bunch; I just find the implications of > that API far too

[go-nuts] Re: rand.Rand.Seed() vs rand.NewSource()

If you use the same seed the source will output the same pseudo-random output. Which is quite useful when you need to be able to replay/predict the random behaviour On Tuesday, 26 March 2019 19:48:27 UTC+1, Liam wrote: > > Could anyone clarify the difference between these two? > > r :=