[go-nuts] Re: howto kill pipe process using gopkg.in/pipe.v2

State.Kill looks promising. On Monday, July 18, 2016 at 10:39:36 AM UTC-7, Walter Garcia wrote: > > Hello. > > Im using pipe.v2 and work fine, but I need cancel the process running, How > can I do it? > > The process is running, but in certain circu

Re: [go-nuts] Understanding HTTP server latencies

On Mon, Jul 18, 2016 at 10:46 AM, Bakul Shah wrote: > A number of nodes and machines and networks are involved in > your test so you need to somehow further isolate the problem. > .. On Mon, 18 Jul 2016 06:03:26 PDT Rayland wrote: > > I have an HTTP server in AWS on an instance with 4 cores

[go-nuts] Re: problems receiving data from a GPS

In GO I get this data buf := make([]byte, 1024) buf: [64 64 153 0 4 50 49 51 71 76 50 48 49 52 48 49 53 49 56 55 0 0 0 0 0 16 1 233 24 140 87 64 25 140 87 68 88 10 0 136 2 0 0 182 29 0 0 4 0 0 0 4 0 7 100 1 17 19 0 3 0 1 17 7 16 23 43 59 76 94 160 0 244 82 243 16 7 0 0 0 0 73 68 68 95 50 49 5

Re: [go-nuts] Re: [security] Go 1.6.3 and 1.7rc2 are released

The pre-announcement on golang-nuts also reiterated this plan :) On Jul 18, 2016 5:04 PM, "Ian Lance Taylor" wrote: > On Mon, Jul 18, 2016 at 4:40 PM, wrote: > > Ah, sounds good. By chance is there an estimated date on that? :D > > Wednesday or Thursday. > > Ian > > > > On Monday, July 18, 201

Re: [go-nuts] Re: [ANN] UniDoc PDF Toolkit for golang

On Monday, July 18, 2016 at 4:45:37 AM UTC-7, rog wrote: > > On 16 July 2016 at 16:33, Daniel Theophanes > wrote: > > I would also note that AGPL is probably unusable in most Go programs > > (statically linked and all). -Daniel > > Why so? You just need to make your program open source, which

Re: [go-nuts] Re: [security] Go 1.6.3 and 1.7rc2 are released

On Mon, Jul 18, 2016 at 4:40 PM, wrote: > Ah, sounds good. By chance is there an estimated date on that? :D Wednesday or Thursday. Ian > On Monday, July 18, 2016 at 2:49:54 PM UTC-7, Ian Lance Taylor wrote: >> >> On Mon, Jul 18, 2016 at 1:09 PM, wrote: >> > Or another example https://github

Re: [go-nuts] Re: [security] Go 1.6.3 and 1.7rc2 are released

Ah, sounds good. By chance is there an estimated date on that? :D On Monday, July 18, 2016 at 2:49:54 PM UTC-7, Ian Lance Taylor wrote: > > On Mon, Jul 18, 2016 at 1:09 PM, > > wrote: > > Or another example https://github.com/golang/go/issues/16333. Its in > master > > but not the release-bra

Re: [go-nuts] Re: Go Oracle: an editor-integrated static analysis tool for Go code comprehension

The Oracle tool is deprecated and I will delete it in October. Please use the Guru tool instead: https://golang.org/s/using-guru thanks alan -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails

Re: [go-nuts] Understanding HTTP server latencies

On Mon, Jul 18, 2016, at 03:13 PM, Rayland wrote: > Any thoughts on how to attack this problem? You could run the tiny example that Peter Waller wrote with the same test and share the results here. If we see the same slowdown pattern then it would eliminate a problem in your code. -- Ian -- Y

Re: [go-nuts] Re: [security] Go 1.6.3 and 1.7rc2 are released

On Mon, Jul 18, 2016 at 1:09 PM, wrote: > Or another example https://github.com/golang/go/issues/16333. Its in master > but not the release-branch.go1.7. Oh, I see. The plan, as discussed at the release meeting at Gophercon but probably never sent to the list, is to do another real release cand

Re: [go-nuts] Re: [security] Go 1.6.3 and 1.7rc2 are released

Or another example https://github.com/golang/go/issues/16333. Its in master but not the release-branch.go1.7. On Monday, July 18, 2016 at 12:31:13 PM UTC-7, Ian Lance Taylor wrote: > > On Mon, Jul 18, 2016 at 12:11 PM, > > wrote: > > Why are the other changes to be released but not related to

Re: [go-nuts] Re: [security] Go 1.6.3 and 1.7rc2 are released

Specifically this one https://github.com/golang/go/issues/16308 but perhaps there are others. On Monday, July 18, 2016 at 12:31:13 PM UTC-7, Ian Lance Taylor wrote: > > On Mon, Jul 18, 2016 at 12:11 PM, > > wrote: > > Why are the other changes to be released but not related to this > security

Re: [go-nuts] Re: [security] Go 1.6.3 and 1.7rc2 are released

On Mon, Jul 18, 2016 at 12:11 PM, wrote: > Why are the other changes to be released but not related to this security > issue not in rc2? To which changes are you referring? Ian > On Monday, July 18, 2016 at 9:59:54 AM UTC-7, Chris Broadfoot wrote: >> >> A security-related issue was recently r

[go-nuts] Re: [security] Go 1.6.3 and 1.7rc2 are released

Why are the other changes to be released but not related to this security issue not in rc2? On Monday, July 18, 2016 at 9:59:54 AM UTC-7, Chris Broadfoot wrote: > > A security-related issue was recently reported in Go's net/http/cgi > package and net/http package when used in a CGI environment.

Re: [go-nuts] pprof where is my time going

On Mon, Jul 18, 2016 at 10:28 AM, ajay aggarwal wrote: > Thanks for the explanation on runtime.mcall and runtime.schedule. Is it true > that if your application gets blocked a lot (say on I/O) then CPU profile > will not help you to figure out where you are getting blocked the most? The > blocked

[go-nuts] Re: [security] Go 1.6.3 and 1.7rc2 are released

Not sure if this is a real issue but I noticed it with rc1 also. Raised a github request here: https://github.com/golang/go/issues/16409 I'm unable to install it on a Mac from .pkg file into any dir except /usr/local/go. On Monday, 18 July 2016 22:29:54 UTC+5:30, Chris Broadfoot wrote: > > A s

Re: [go-nuts] Understanding HTTP server latencies

A number of nodes and machines and networks are involved in your test so you need to somehow further isolate the problem. In place of the go http server, you can just put a simple C/C++ based listener that accepts connections and closes them right away -- that should measure raw connection accept r

[go-nuts] howto kill pipe process using gopkg.in/pipe.v2

Hello. Im using pipe.v2 and work fine, but I need cancel the process running, How can I do it? The process is running, but in certain circumstances I need to cancel. this is my code p := pipe.Line( pipe.Exec("command1", args_command1...), pipe.Exec("command2", args_command2...), ) outp

Re: [go-nuts] pprof where is my time going

Thanks for the explanation on runtime.mcall and runtime.schedule. Is it true that if your application gets blocked a lot (say on I/O) then CPU profile will not help you to figure out where you are getting blocked the most? The blocked goroutines will not show up in the CPU profile samples.. On

[go-nuts] [security] Go 1.6.3 and 1.7rc2 are released

A security-related issue was recently reported in Go's net/http/cgi package and net/http package when used in a CGI environment. Go 1.6.3 and Go 1.7rc2 will contain a fix for this issue. Go versions 1.0-1.6.2 and 1.7rc1 are vulnerable to an input validation flaw in the CGI components resulting

Re: [go-nuts] Re: An efficient runtime expression evaluation

I think this pretty much covers it _, err := VirtualProtect(fn.body, 0x40) if err != nil { panic(err) } // OH GOD WHAT HAVE I DONE??? type callstub struct{ fn func(*Memory) } Excellent and worrying work :-) A 2x difference between interpreted and native is pretty rad. It strongly remind

Re: [go-nuts] Re: Strange results from append

Hi Kortschak, That's interesting! I've actually never had use for 3 index slicing in the past, so I didn't think of this. It definitely achieves the desired result, but also forces two allocations. I still find creating with the full capacity in one go and copying / appending to be faster. fun

Re: [go-nuts] Re: An efficient runtime expression evaluation

Impressive AND aggressive. ;-) From: on behalf of Egon Date: Monday, July 18, 2016 at 9:07 AM To: golang-nuts Cc: , Subject: Re: [go-nuts] Re: An efficient runtime expression evaluation On Monday, 18 July 2016 13:27:09 UTC+3, Michael Jones wrote: Anything much faster than this needs ve

Re: [go-nuts] Re: An efficient runtime expression evaluation

On Monday, 18 July 2016 13:27:09 UTC+3, Michael Jones wrote: > > Anything much faster than this needs vector operations in the interpreter > so the “get to the OP function” overhead is once per time series rather > than once per element in the series. > I managed to make it a little faster https

Re: [go-nuts] Streaming deflate - can't reliably read chunks as they arrive instead of the entire stream

I initially tried that. Turns out deflate needs to maintain the same sliding window across messages depending on whether or not context takeover is being used - https://tools.ietf.org/html/rfc7692#section-7 On Saturday, July 16, 2016 at 2:04:59 AM UTC-4, Tamás Gulácsi wrote: > > What if you crea

Re: [go-nuts] Understanding HTTP server latencies

Check also that you dont have any ulimits that are limiting the maximum concurrent open files, each socket is a file handle, if you dont open it up you can starve the vegita host of outbound connections. It may be worth firing up 10 t1.micro instances and run 10th of the load from each. On 18 Jul

Re: [go-nuts] Understanding HTTP server latencies

The client and the server are two separate machines in aws. No middlewares and proxies. I don't get any network related error. On Jul 18, 2016 17:48, "Peter Waller" wrote: > If you run it on the same server as the host, does it perform differently > there? For example, did you rule out network s

Re: [go-nuts] Understanding HTTP server latencies

If you run it on the same server as the host, does it perform differently there? For example, did you rule out network saturation effects? Do you have any HTTP middleware or proxies in the way? -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To u

[go-nuts] Mercado Libre SDK

Hello folks, I made a SDK for Mercadolibre integration. I'll be happy if you help me to improve my code. https://github.com/tiaguinho/mercadolibre-go-sdk Thanks. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group an

Re: [go-nuts] Segmentaion fault / static binary

FWIW, the "github.com/xeodou/go-sqlcipher" library isn't being linked correctly, and it seems to be trying to load /lib/x86_64-linux-gnu/libcrypto.so at runtime. Not sure what's at fault off hand, but "github.com/xeodou/go-sqlcipher" might be making some assumptions about being dynamically lin

Re: [go-nuts] Understanding HTTP server latencies

The command I used is: vegeta attack -targets=address.txt -body=request.txt -duration=1s -rate=1000 > output.txt On Monday, July 18, 2016 at 4:34:52 PM UTC+3, Peter Waller wrote: > > It really depends on what you're doing while handling your requests. It > may or may not be reasonable. Are you t

Re: [go-nuts] Understanding HTTP server latencies

Any thoughts on how to attack this problem? On Monday, July 18, 2016 at 4:46:26 PM UTC+3, Michael Jones wrote: > > When you move the rate up by 5x, from 1k => 5k, your wait time moves up by > 2846x. That is suspicious in any system, language, etc. ;-) > > > > *From: *> on behalf of Rayland < >

Re: [go-nuts] Understanding HTTP server latencies

I thought it was self explanatory, the handler does nothing, just returning an error. On Monday, July 18, 2016 at 4:34:52 PM UTC+3, Peter Waller wrote: > > It really depends on what you're doing while handling your requests. It > may or may not be reasonable. Are you touching external resources

Re: [go-nuts] What dependency management tool do you use?

On Saturday, July 16, 2016 at 3:17:11 PM UTC+2, Peter Mogensen wrote: > > It's somewhat the same as we use: > * Don't use "go get" > * Have GOTPATH=${PWD} in project root. > * Have a /src directory in the project containing a link to project root > (often ../..) at the package name. > * Use

Re: [go-nuts] Segmentaion fault / static binary

On Mon, 18 Jul 2016 05:38:50 -0700 (PDT) kumargv wrote: > But for me still it is giving same error > I also updated to amd64 with go1.7rc1 > > these are the dependence of the sample program > > linux-vdso.so.1 => (0x7ffca8fba000) > libcrypto.so.1.0.0 > => /lib/x86_64-linu

Re: [go-nuts] Understanding HTTP server latencies

When you move the rate up by 5x, from 1k => 5k, your wait time moves up by 2846x. That is suspicious in any system, language, etc. ;-) From: on behalf of Rayland Date: Monday, July 18, 2016 at 6:03 AM To: golang-nuts Subject: [go-nuts] Understanding HTTP server latencies 5k req/s Requ

[go-nuts] Texture codecs : DXT, PVRTC, ETC1

Hello Gophers I consider reading and writing lossy fixed-rate textures in formats DXT , PVRTC and ETC1 . I will try [1] which

Re: [go-nuts] Understanding HTTP server latencies

It really depends on what you're doing while handling your requests. It may or may not be reasonable. Are you touching external resources such as a database? Can you provide a minimal example to reproduce? It would also be useful if you supplied the exact commands you are running. I have managed

Re: [go-nuts] Segmentaion fault / static binary

Sorry, I don't have any further suggestions. The only other things that spring to mind: * I tested on Ubuntu 15.10, with all of my packages uptodate. The distro could matter, in principle. * Is everything uptodate? Do you have the latest version of github.com/xeodou/go-sqlcipher and its dependenci

[go-nuts] Understanding HTTP server latencies

I have an HTTP server in AWS on an instance with 4 cores and 8g of memory. The server is not processing anything, just replying with 500. I have another machine in AWS issuing POST requests with Vegeta. These are my results: *10k req/s * Requests [total, rate]1, 9628.13

Re: [go-nuts] Segmentaion fault / static binary

But for me still it is giving same error I also updated to amd64 with go1.7rc1 these are the dependence of the sample program linux-vdso.so.1 => (0x7ffca8fba000) libcrypto.so.1.0.0 => /lib/x86_64-linux-gnu/libcrypto.so.1.0.0 (0x7fa93c071000) libdl.so.2 => /lib/

Re: [go-nuts] Segmentaion fault / static binary

go 1.6.2 OS 16.04 LTS ubuntu On Monday, July 18, 2016 at 5:25:21 PM UTC+5:30, Peter Waller wrote: > > I just tested this here on amd64 with go1.7rc1, and it works fine with no > crash, so I don't know why it is crashing for you. > > What version of go are you using? > -- You received this messa

Re: [go-nuts] looking for the equivelant golang code in the aws s3 sdk, but have not found it yet. Anyone help here??? Thanks.

Here's an example. It uses the machine's role credentials automatically. If you want to specify a secret manually, you'll have to read the documentation. https://github.com/aws/aws-sdk-go/ http://aws.amazon.com/sdk-for-go/ I can't guarantee it's uptodate, but something similar to this should work

Re: [go-nuts] Segmentaion fault / static binary

I just tested this here on amd64 with go1.7rc1, and it works fine with no crash, so I don't know why it is crashing for you. What version of go are you using? -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and sto

Re: [go-nuts] Re: [ANN] UniDoc PDF Toolkit for golang

On 16 July 2016 at 16:33, Daniel Theophanes wrote: > I would also note that AGPL is probably unusable in most Go programs > (statically linked and all). -Daniel Why so? You just need to make your program open source, which shouldn't be too onerous a requirement I'd've thought. -- You received t

Re: [go-nuts] [ANN] Nexer 1.1.1 code name: Billy

On Sun, 17 Jul 2016 00:55:27 -0700 (PDT) Val wrote: > ok but what is Nexer? https://groups.google.com/d/topic/golang-nuts/cbKFvK4pKPc/discussion But sure I think it would not hurt if the author decorated the news with a simple synopsis like "Nexer, the ... doing ... and ... for ...". -- You r

Re: [go-nuts] Re: An efficient runtime expression evaluation

Anything much faster than this needs vector operations in the interpreter so the “get to the OP function” overhead is once per time series rather than once per element in the series. From: on behalf of Egon Date: Monday, July 18, 2016 at 1:32 AM To: golang-nuts Cc: Subject: [go-nuts] Re:

[go-nuts] Re: [ANN] UniDoc PDF Toolkit for golang

Yes, it shouldn't take long to implement. On Mon, Jul 18, 2016 at 9:02 AM, Ali Anwar wrote: > Any plans to add clip/crop pdf files? > > On Saturday, July 16, 2016 at 5:22:00 PM UTC+2, ah...@owlglobal.io wrote: >> >> Hi all. >> >> Today we are releasing UniDoc version 1.0, a comprehensive open so

[go-nuts] Re: DB application design: Embedding vs Having an ID field pointing to resource

Introducing new types just to show few details is what I'd like to avoid. I think second approach (mine and yours) is the most flexible, idiomatic way to go. But embedding directly has the disadvantage that all JSON fields must be prefixed to avoid ambiguity ("org-id", "team-id"). Tagging all f

Re: [go-nuts] scheduling non determinism

> > > For concurrent programs, obviously the program needs to be race-free -- no > reads of data that could hold different values based on grouting scheduling > of writes (using happens-before). > > Indeed, this is the definition of "racy" we're interested in. As Ian pointed out, this is disti

[go-nuts] Re: [ANN] UniDoc PDF Toolkit for golang

Any plans to add clip/crop pdf files? On Saturday, July 16, 2016 at 5:22:00 PM UTC+2, ah...@owlglobal.io wrote: > > Hi all. > > Today we are releasing UniDoc version 1.0, a comprehensive open source PDF > toolkit written in Go. Please see our release post > http://unidoc.io/news/launching-unidoc

[go-nuts] Re: An efficient runtime expression evaluation

On Monday, 18 July 2016 11:13:08 UTC+3, Egon wrote: > > > > On Monday, 18 July 2016 10:30:14 UTC+3, Egon wrote: >> >> On Monday, 18 July 2016 03:11:29 UTC+3, ondrej...@gmail.com wrote: >>> >>> Cheers, I tried replicating my endeavours ( >>> https://play.golang.org/p/Qxoo2ASac6), sorry if it's sti

[go-nuts] Re: An efficient runtime expression evaluation

On Monday, 18 July 2016 10:30:14 UTC+3, Egon wrote: > > On Monday, 18 July 2016 03:11:29 UTC+3, ondrej...@gmail.com wrote: >> >> Cheers, I tried replicating my endeavours ( >> https://play.golang.org/p/Qxoo2ASac6), sorry if it's still too verbose. >> It's essentially rewriting the inbuilt ast.No

[go-nuts] Re: DB application design: Embedding vs Having an ID field pointing to resource

On Monday, 18 July 2016 10:33:44 UTC+3, fazal wrote: > > Fellow gophers, > > I'm having this dilemma of whether to embed related struct, or to have an > ID field pointing to resource in the DB. > Note ensure that your ID is not generated from the Name, team names change and if you rely on it b

[go-nuts] DB application design: Embedding vs Having an ID field pointing to resource

Fellow gophers, I'm having this dilemma of whether to embed related struct, or to have an ID field pointing to resource in the DB. Say I have something like these types defined. type Team struct{ ID string Name string } type Organization struct { ID string Name string } Now m

[go-nuts] Re: An efficient runtime expression evaluation

PS: you may want to research and learn how Forth interpreters are implemented, they have similar problems. On Monday, 18 July 2016 10:30:14 UTC+3, Egon wrote: > > On Monday, 18 July 2016 03:11:29 UTC+3, ondrej...@gmail.com wrote: >> >> Cheers, I tried replicating my endeavours ( >> https://play.g

[go-nuts] Re: An efficient runtime expression evaluation

On Monday, 18 July 2016 03:11:29 UTC+3, ondrej...@gmail.com wrote: > > Cheers, I tried replicating my endeavours ( > https://play.golang.org/p/Qxoo2ASac6), sorry if it's still too verbose. > It's essentially rewriting the inbuilt ast.Node into a simpler nested > struct and then walking it. > > In

[go-nuts] DB Application design: Embedding types vs Having an ID field

Fellow gophers, I'm having this dilemma of whether to embed related struct, or to have an ID field pointing to resource in the DB. Say I have something like these types defined. type Team struct{ ID string Name string } type Organization struct { ID string Name string } Now m

[go-nuts] Segmentaion fault / static binary

This is the Link of program what i am compiling https://play.golang.org/p/drJGhsWiEi when i am using- go build program.go ,it generating ->program(binary) file ./program program: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2