[go-nuts] sync/mutex locking race condition issues

Hi, I am having issues with some concurrency and race conditions. I believe this is not doing what I think it does. IE I am thinking this would allow locking of any variable in the struct however it does not seem to be applying to buffer of type bytes.Buffer. What am I missing here? I have:

[go-nuts] go-grpc question

Hello, I intend to use grpc between two fixed endpoints (client and server) where the client receives multiple requests (the client serves as a proxy) which in turn sends a grpc request to the server. I wanted to know of the following would be considered good practice: a) For every request tha

Re: [go-nuts] Why can runtime.procyield declare its argument stack size to be zero?

Thanks. Now I feel a bit less crazy. -jwb On Tue, Oct 16, 2018 at 5:14 PM Ian Lance Taylor wrote: > On Thu, Oct 11, 2018 at 3:01 PM, Jeffrey Baker wrote: > > > > I'm trying to learn how to safely use this asm, and I don't understand > some > > of the existing asm in the runtime package. From

Re: [go-nuts] Re: Generics: an unwelcome conclusion and a proposal

The easiest solution is that []int IS A IntList by definition, no ? Meaning that an “slice” has defined methods Len(), and At(). I would personally define other methods on slice too for convenience (like, Insert, Delete). The [] notation is just syntactic sugar for slice.At(). When used as a lef

Re: [go-nuts] Command line password manager using AES symmetric key encryption, Argon2 KDF, Key-Agent and Keepass importer

I did some reading on the yubikey, and it works pretty much how I expected, and I’m pretty sure my assessment still holds. (And as an aside, up until the latest release they were all completely broken… https://arstechnica.com/information-technology/2017/10/crypto-failure-cripples-millions-of-hig

Re: [go-nuts] Why can runtime.procyield declare its argument stack size to be zero?

On Thu, Oct 11, 2018 at 3:01 PM, Jeffrey Baker wrote: > > I'm trying to learn how to safely use this asm, and I don't understand some > of the existing asm in the runtime package. From amd64.s: > > TEXT runtime·procyield(SB),NOSPLIT,$0-0 > MOVL cycles+0(FP), AX > > My understanding of $0-0 is it'

Re: [go-nuts] Re: Generics: an unwelcome conclusion and a proposal

On Tue, Oct 16, 2018 at 3:33 AM alanfo wrote: > I would also disallow overloading of the =, :=, <-, ..., [], {}, () and > yes - equality operators - as well because I believe to do otherwise would > be very confusing. > If overloading [] were disallowed, how would one write a generic function ta

Re: [go-nuts] Generics with adaptors

Quoting Patrick Smith (2018-10-16 18:32:48) >The union function could verify that the two adaptors are the same, >using the == operator, and panic if not. However, this breaks down if >the adaptors, instead of being defined as struct{}, are defined as >types which don't support ==.

Re: [go-nuts] Generics with adaptors

On Tue, Oct 16, 2018 at 3:21 PM Ian Denhardt wrote: > Quoting Patrick Smith (2018-10-16 18:04:05) > >One way to avoid this is to supply the adaptor when the Set is > created, > >store it in the Set, and thereafter used the stored adaptor instead of > >requiring an adaptor parameter. >

Re: [go-nuts] Generics with adaptors

Quoting Patrick Smith (2018-10-16 18:04:05) >One way to avoid this is to supply the adaptor when the Set is created, >store it in the Set, and thereafter used the stored adaptor instead of >requiring an adaptor parameter. This works for insert/member, but what about union, which takes

Re: [go-nuts] Generics with adaptors

On Tue, Oct 16, 2018 at 12:01 PM Ian Denhardt wrote: > * We don't actually need an adaptor for the zero value, since we can > just declare a variable of the generic type: > > func MyFn(type T) { > // x is the zero value, per usual initialization rules: > var x T > True. Thi

Re: [go-nuts] Generics: an unwelcome conclusion and a proposal

Quoting Eric Raymond (2018-10-16 17:28:11) >Fair enough. But is there any way to have a contract system of *any* >kind that doesn't have the identical problem?� Linked elsewhere in this thread, but I sketched something that I think does the trick: https://gist.github.com/zenhack/ad50

Re: [go-nuts] Generics: an unwelcome conclusion and a proposal

On Tue, Oct 16, 2018 at 2:28 PM, Eric Raymond wrote: > > On Tuesday, October 16, 2018 at 4:52:54 PM UTC-4, Ian Denhardt wrote: >> >> The trouble is that (in the case where you compile using the implements >> <, rather than throwing an error) the type signature no longer tells you >> what the const

Re: [go-nuts] Re: Generics with adaptors

On Tue, Oct 16, 2018 at 5:44 AM Eric Raymond wrote: > On Tuesday, October 16, 2018 at 6:34:10 AM UTC-4, Patrick Smith wrote: >> >> Yet another generics discussion at >> https://gist.github.com/pat42smith/ccf021193971f6de6fdb229d68215302 >> > > I think it fails Ian Lance Taylor's smoke test. > I

Re: [go-nuts] Generics: an unwelcome conclusion and a proposal

On Tuesday, October 16, 2018 at 4:52:54 PM UTC-4, Ian Denhardt wrote: > > The trouble is that (in the case where you compile using the implements > <, rather than throwing an error) the type signature no longer tells you > what the constraints actually are; this information is only in the body

[go-nuts] Re: Generics with adaptors

An interesting and (for me at least) novel approach to contract-free generics. Despite the suggestions towards the end, it's still too verbose for my taste but I did find it reassuring that, even without operator overloading (Eric's proposal), there would still be a plausible way to write gener

Re: [go-nuts] Generics: an unwelcome conclusion and a proposal

On Tuesday, October 16, 2018 at 4:41:53 PM UTC-4, Dave MacFarlane wrote: > > Now I'm confused about what problem regarding generics you're trying > to solve with operator overloading. If you can't assume anything about > the meaning of an operator other than "it returns a bool", how could a >

Re: [go-nuts] Generics: an unwelcome conclusion and a proposal

Quoting Eric Raymond (2018-10-16 16:37:01) > you either compile "a < b" using the "implements <" method of the > concrete type or throw an error. > This means that a change in the generic function, which happens to > introduce a new use of the parameter, can cause a failure at the >

Re: [go-nuts] Generics: an unwelcome conclusion and a proposal

On Tuesday, October 16, 2018 at 4:17:36 PM UTC-4, Ian Denhardt wrote: > > What is this intended to buy us? Is this as Ian T suggests in lieu of > any kind of contract system? Oh , no. You *need* a contract system (or at least my implements clause) so you can know if a < b has a meaning when

Re: [go-nuts] Generics: an unwelcome conclusion and a proposal

Quoting Dave MacFarlane (2018-10-16 16:40:59) > (Also, does this mean the compiler wouldn't be able to make any > optimization assumptions regarding whether an operation is > commutative/associative/distributive?) This is true regardless, because we aren't actually *enforcing* these properties; t

Re: [go-nuts] Generics: an unwelcome conclusion and a proposal

On Tue, Oct 16, 2018 at 4:14 PM Eric Raymond wrote: > If the alternative is requiring programmers to remember pre-cooked > relationships between different operators that may or may not be appropriate > for what he or she is trying to model, then I embrace this "problem". > > It's up to the progr

Re: [go-nuts] Issue with creating file on aws lambda

I'm pretty sure that the only writeable file system on Lambda in under /tmp. You're not checking the error return from os.MkdirAll, but that call is probably failing before you get to os.Create. Also keep in mind that each Lambda instance is limited to 512 MB of /tmp space: https://docs.aws.amazon.

Re: [go-nuts] Generics: an unwelcome conclusion and a proposal

On Tuesday, October 16, 2018 at 4:03:16 PM UTC-4, Ian Lance Taylor wrote: > > It's a feasible approach. But unless I misunderstand, testing > arguments at the call site means that you've discarded contracts. > I don't understand that claim. A contract (in my plan, an "implements" clause) is

Re: [go-nuts] Generics: an unwelcome conclusion and a proposal

Quoting Eric Raymond (2018-10-16 16:14:46) >It's up to the programmer to implement things like commutativity.� I >don't think the language should pre-specify whether < is a partial or >total ordering.� Any choice of this kind the language makes will >inevitably turn out wrong a s

Re: [go-nuts] Generics: an unwelcome conclusion and a proposal

Quoting Ian Lance Taylor (2018-10-16 16:02:57) > On Tue, Oct 16, 2018 at 8:39 AM, Eric Raymond wrote: > > > > New rule: A function on variables of undefined formal-argument types > > compiles to a template (not a textual template - we don't want identifier > > capture). At each callsite of the fu

Re: [go-nuts] Remove path from error messages

On Tue, Oct 16, 2018 at 11:57 AM, Rich wrote: > Hi and Thanks Peter for your reply! I have compiled this on my mac, and am > running it on a linux system. I compile it like this: > > GOOS=linux GOARCH=amd64 go build -o binaries/linux64/mysqlrun mysqlrun.go > > Then I copy that binary to the ser

Re: [go-nuts] Generics: an unwelcome conclusion and a proposal

(Sorry about the post fragment that got away from me.) On Tuesday, October 16, 2018 at 3:33:58 PM UTC-4, Ian Denhardt wrote: > > > The alternative though is having to implement several different methods > with obvious implementations in terms of one another, and make sure > they're consistent.

Re: [go-nuts] Generics: an unwelcome conclusion and a proposal

On Tue, Oct 16, 2018 at 8:39 AM, Eric Raymond wrote: > > New rule: A function on variables of undefined formal-argument types > compiles to a template (not a textual template - we don't want identifier > capture). At each callsite of the function, the undefined types in the > formals are bound to

Re: [go-nuts] Generics: an unwelcome conclusion and a proposal

Quoting Eric Raymond (2018-10-16 15:57:49) >I don't undetstand rte q rte q? I assume this is a typo, but I'm not sure what it was supposed to be... -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop recei

[go-nuts] Re: Command line password manager using AES symmetric key encryption, Argon2 KDF, Key-Agent and Keepass importer

Thanks for giving it a go! cheers, Matthias Am Dienstag, 16. Oktober 2018 13:32:20 UTC+2 schrieb Thorsten Sommer: > > Thank you Matthias, for sharing your work. I find your password manager > useful. Keep the good work. > > Am Sonntag, 14. Oktober 2018 17:49:04 UTC+2 schrieb Matthias Schmidt: >

Re: [go-nuts] Generics: an unwelcome conclusion and a proposal

On Tuesday, October 16, 2018 at 3:33:58 PM UTC-4, Ian Denhardt wrote: > > > The partial vs. total order thing brings up another issue that I think > needs to be kept in mind: what are the contracts for the various > operators? > I don't undetstand rte q -- You received this message because

Re: [go-nuts] Re: Command line password manager using AES symmetric key encryption, Argon2 KDF, Key-Agent and Keepass importer

And here it is: https://github.com/ms140569/loki/releases/tag/1.2.0 Thanks to your guy's input the key-agent should be now way more secure. cheers, Matthias Am Dienstag, 16. Oktober 2018 20:31:42 UTC+2 schrieb Matthias Schmidt: > > Hi Christopher + Eric, > > thanks for your feedback. You are r

[go-nuts] Issue with creating file on aws lambda

Hello, I am trying to make function which will down file fro aws s3 and do some image resizing. I am having issue with os.Create, when I run locally on ec2 machine it works fine but when I run on lambda directly I get error file not found package main import ( "github.com/aws/aws-sdk-go

Re: [go-nuts] Re: Command line password manager using AES symmetric key encryption, Argon2 KDF, Key-Agent and Keepass importer

Maybe we're talking about different things. Are you thinking of TOTP 2FA tokens? Your arguments do apply to those. I'm not talking about those. I'm talking about devices like a yubikey, which is essentially a a poor person's HSM. On Mon, Oct 15, 2018 at 7:21 PM robert engels wrote: > > That is n

Re: [go-nuts] Generics: an unwelcome conclusion and a proposal

Quoting Eric Raymond (2018-10-16 13:41:47) >On Tuesday, October 16, 2018 at 1:23:20 PM UTC-4, Dave MacFarlane >wrote: > > [...] > > Would there be any rules defined for relationships between > operators? > For instance, if the "<" operator is defined does "<=" come for free >

Re: [go-nuts] Replacing the current go process with os.execvpe

Thanks, syscall.Exec seems to be what I want then. Am Dienstag, 16. Oktober 2018 17:02:46 UTC+2 schrieb Ian Lance Taylor: > > On Tue, Oct 16, 2018 at 7:13 AM, Mirko Friedenhagen > > wrote: > > > > I am on my way to replace a Python script which writes several > configuration > > files before

Re: [go-nuts] Re: Go standard library documentation for older Go versions

Thanks for the helpful suggestions! The GO docs do indeed have a version on the right edge of the screen, I completely failed to see it. Exactly what I wanted. Also I appreciate the tip about downloading local sources, that's always handy. Sorry for the noise. On Tue, Oct 16, 2018 at 2:44 PM Jan M

Re: [go-nuts] Generics with adaptors

I write this kind of code a lot when working in Elm (whose generics are in a similar spot to the place you suggest). It's not the worst, and there various approaches in related languages use to make the "adaptors" more ergonomic. I still like the idea of using interfaces to express constraints bet

Re: [go-nuts] Remove path from error messages

Hi and Thanks Peter for your reply! I have compiled this on my mac, and am running it on a linux system. I compile it like this: GOOS=linux GOARCH=amd64 go build -o binaries/linux64/mysqlrun mysqlrun.go Then I copy that binary to the server I am running it on and if there is an error -- it s

Re: [go-nuts] Re: Go standard library documentation for older Go versions

On Tue, Oct 16, 2018 at 8:39 PM Agniva De Sarker < agniva.quicksil...@gmail.com> wrote: > It already does. Example - https://golang.org/pkg/net/http/#SameSite I cannot see anything like "introduced in version" at that page? Anyone knows why? (Using Chrome Verze 69.0.3497.100 (Oficiální sestavení)

Re: [go-nuts] Debian package for Go 1.11 on the way?

On Tue, Oct 16, 2018 at 4:12 PM Wojciech S. Czarnecki wrote: > On Tue, 16 Oct 2018 01:57:17 -0700 (PDT) > Lasse Westh-Nielsen wrote: > > > Have been using https://github.com/golang/go/wiki/Ubuntu, does anybody > know > > if there is a 1.11 package on the way? > > wiki/Ubuntu says "The Go project

[go-nuts] Re: Go standard library documentation for older Go versions

Online API docs are just for the latest release and the master branch. But if you have the version you want locally installed, you can just spin up godoc and point to the goroot and browse it. > I would love it if the https://golang.org/pkg/ documentation had "introduced in version..." notation

Re: [go-nuts] Remove path from error messages

Error messages don't include any contextual information by default. If the path to a Go file is in there, it's because whatever created the error message (or modified it at some point) put it there. Where is that error created, and what touches it as it flows through the call stack to the logging s

Re: [go-nuts] Re: Command line password manager using AES symmetric key encryption, Argon2 KDF, Key-Agent and Keepass importer

Hi Christopher + Eric, thanks for your feedback. You are right, i really underestimated the risk of such attacks. I will lock the key-holding memory in the next release. cheers, Matthias Am Montag, 15. Oktober 2018 23:13:32 UTC+2 schrieb Christopher Nielsen: > > On Mon, Oct 15, 2018 at 1:28

[go-nuts] Remove path from error messages

I apologize if this has been asked before but I searched google and this group and didn't find it. How do you remove the path from the error messages? So I have a valid error: 2018/10/16 18:13:12 [error] in main.checkMaster[/Users/rich/go/mysqlrun/mysqlrun.go:739] Error 1045: Access denied f

Re: [go-nuts] Generics: an unwelcome conclusion and a proposal

On Tuesday, October 16, 2018 at 1:23:20 PM UTC-4, Dave MacFarlane wrote: > > Why is the implements keyword a better solution than magic names? > Because you get syntactic uniformity with primitive types without claiming namespace you don't need. It's more minimalist. Would there be any rule

Re: [go-nuts] Generics: an unwelcome conclusion and a proposal

Why is the implements keyword a better solution than magic names? Magic names feel more Go-ish to me in the sense that interface implementations already eschew the implements keyword (unlike most other languages) and don't require any syntactic changes to the language. Would there be any rules def

[go-nuts] Re: Generics: an unwelcome conclusion and a proposal

On Tuesday, October 16, 2018 at 12:24:59 PM UTC-4, alanfo wrote: > > With regard to your reply to Ian, I'm afraid I can't agree with you that > the type parameters shouldn't be specified 'up front'. That's just too > 'dynamic' for me and not very go-like. I'd imagine it would give the > compil

Re: [go-nuts] Generics: an unwelcome conclusion and a proposal

Quoting Ian Lance Taylor (2018-10-16 09:44:00) > It's not clear to me what other aspects of various generic proposals > you are picking up here. How are you imagining that we would write > the function that merges two channels? With the current design draft > that looks something like this: > >

[go-nuts] Re: Generics: an unwelcome conclusion and a proposal

I'm not sure whether the likes of = and := would be classed as operators or punctuation in Go though the former is certainly an operator in C++ where (very confusingly IMO) it can be overloaded and sometimes is. Although I wouldn't like to see these symbols overloaded in Go I don't have a probl

Re: [go-nuts] Generics: an unwelcome conclusion and a proposal

On Tue, 16 Oct 2018 08:39:32 -0700 (PDT) Eric Raymond wrote: > New rule: A function on variables of undefined formal-argument types > compiles to a template (not a textual template - we don't want identifier > capture). At each callsite of the function, the undefined types in the > formals ar

[go-nuts] Re: Debian package for Go 1.11 on the way?

2018. október 16., kedd 14:38:08 UTC+2 időpontban Lasse Westh-Nielsen a következőt írta: > > Hey, > > Have been using https://github.com/golang/go/wiki/Ubuntu, does anybody > know if there is a 1.11 package on the way? > > Regards, > > Lasse > > I use 'go get gopkg.in/niemeyer/godeb.v1/cmd/gode

Re: [go-nuts] Generics: an unwelcome conclusion and a proposal

On Tuesday, October 16, 2018 at 9:44:23 AM UTC-4, Ian Lance Taylor wrote: > > It's not clear to me what other aspects of various generic proposals > you are picking up here. The answer is "none of them". That wasn't my goal, because all the previous generics proposals I have seen struck me as

Re: [go-nuts] Go standard library documentation for older Go versions

On Tue, 16 Oct 2018 07:38:09 -0700 (PDT) acon...@redhat.com wrote: > I have not been able to find online API doc for older Go standard library > versions, where would I find this? Apologies if it's in an obvious place > and I missed it. Go library docs are sourced from the source, so all old do

Re: [go-nuts] Replacing the current go process with os.execvpe

On Tue, Oct 16, 2018 at 4:14 PM Mirko Friedenhagen wrote: > Is it OK to just call something like `syscall.Exec("/bin/bash", args, os.Environ())` I'd recommend to first try exec.Command . -- -j -- You received this message because you are subscribed to

Re: [go-nuts] Replacing the current go process with os.execvpe

On Tue, Oct 16, 2018 at 7:13 AM, Mirko Friedenhagen wrote: > > I am on my way to replace a Python script which writes several configuration > files before replacing itself with another program (e.g. bash). For that I > use https://docs.python.org/3/library/os.html#os.execv. > > Is there any equiva

[go-nuts] Go standard library documentation for older Go versions

I have not been able to find online API doc for older Go standard library versions, where would I find this? Apologies if it's in an obvious place and I missed it. I would love it if the https://golang.org/pkg/ documentation had "introduced in version..." notations like https://docs.python.org

[go-nuts] Replacing the current go process with os.execvpe

Hello everybody, I am on my way to replace a Python script which writes several configuration files before replacing itself with another program (e.g. bash). For that I use https://docs.python.org/3/library/os.html#os.execv. Is there any equivalent in Golang? I do not use any fancy go routines

Re: [go-nuts] Debian package for Go 1.11 on the way?

On Tue, 16 Oct 2018 01:57:17 -0700 (PDT) Lasse Westh-Nielsen wrote: > Have been using https://github.com/golang/go/wiki/Ubuntu, does anybody know > if there is a 1.11 package on the way? wiki/Ubuntu says "The Go project's official download page is at https://golang.org/dl/."; There you'll fi

Re: [go-nuts] Generics: an unwelcome conclusion and a proposal

On Mon, Oct 15, 2018 at 7:24 PM, Eric Raymond wrote: > > Recent discussion of possible generics designs has forced me to a conclusion > I'm not happy with, because it requires a feature-cluster that I thought I > was glad to be leaving behind in Python. That is this: > > The simplest and most ef

Re: [go-nuts] Temporary files in go

On 12/10/2018 12.35, Robert Engels wrote: > Which is not Windows, which is giving up a lot of options, and is important > to some people, where as just using tmp files is ok. I am not even sure if > windows supports deleting an open file yet. I believe the default behavior is no it does not. --

[go-nuts] Re: Generics with adaptors

On Tuesday, October 16, 2018 at 6:34:10 AM UTC-4, Patrick Smith wrote: > > Yet another generics discussion at > https://gist.github.com/pat42smith/ccf021193971f6de6fdb229d68215302 > > This one looks at what programmers would be able to do if very basic > generics were added to Go, without contr

[go-nuts] Debian package for Go 1.11 on the way?

Hey, Have been using https://github.com/golang/go/wiki/Ubuntu, does anybody know if there is a 1.11 package on the way? Regards, Lasse -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails fr

[go-nuts] Re: Generics: an unwelcome conclusion and a proposal

On Tuesday, October 16, 2018 at 6:33:26 AM UTC-4, alanfo wrote: > > However, I think it's important to learn the lessons of the past and not > follow languages such as C++ or Scala where you can overload virtually > anything or even make up your own operators which can result in confusing > or e

[go-nuts] Re: Command line password manager using AES symmetric key encryption, Argon2 KDF, Key-Agent and Keepass importer

Thank you Matthias, for sharing your work. I find your password manager useful. Keep the good work. Am Sonntag, 14. Oktober 2018 17:49:04 UTC+2 schrieb Matthias Schmidt: > > Hi Gophers, > > I’ve created a command line password manager in the style of the “pass” > utility by Jason A. Donenfeld (h

[go-nuts] Re: Generics with adaptors

I kind of like this idea. Contracts seem likely to introduce all kinds of complexity, and with a bit more explicit code, just generics without contracts could work just fine. It's definitely the simplest implementation of generics that could work. -- You received this message because you are s

[go-nuts] Re: Generics: an unwelcome conclusion and a proposal

One other advantage of Eric's proposal that has just occurred to me is that folks who dislike operator overloading wouldn't have to use it at all - they could just use the named methods. The only people who would need to use it would be those writing unified generic functions/methods who would

[go-nuts] Generics with adaptors

Yet another generics discussion at https://gist.github.com/pat42smith/ccf021193971f6de6fdb229d68215302 This one looks at what programmers would be able to do if very basic generics were added to Go, without contracts. Generic functions may not use methods or operators of their type parameters. Th

[go-nuts] Re: Generics: an unwelcome conclusion and a proposal

Well, whatever you may think of it, there's no doubt that a lot of the problems we currently have with generic constraints would go away if operator overloading were introduced into Go 2. Personally, I wouldn't be dismayed if this were to happen. A lot of my stuff is mathematical in nature and

Re: [go-nuts] Understanding the doc (why can't I?)

I agree that rand.Shuffle could have used an interface type that's a subset of sort.Interface. I'm not sure why it didn't, although of course it's easy to go from one to the other: func main() { x := []int{1, 2, 3, 4, 5, 6, 7, 8, 9} xi := sort.IntSlice(x) rand.Shuffle(x

Re: [go-nuts] Re: Command line password manager using AES symmetric key encryption, Argon2 KDF, Key-Agent and Keepass importer

The attack does not require the attacker to have root on the compromised machine. It does, however, require the page file not to be encrypted, as is common on Linux and Unix systems. The attack I've described requires physical access, e.g. by quickly copying the hard disk. There are special too