Re: [go-nuts] [ANN] gometalinter v2.0.0 released - much faster linting

On Mon, 4 Dec 2017 21:16:30 -0800 (PST) Alec Thomas wrote: > Hello, > > Through the efforts of many contributors, and in particular those of > Daniel Nephin, v2.0.0 has been released. You can grab it here: > > https://github.com/alecthomas/gometalinter/releases/tag/v2.0.0 > On behalf of m

Re: [go-nuts] [ANN] gometalinter v2.0.0 released - much faster linting

On 05/12/2017 05:16, Alec Thomas wrote: Hello, Through the efforts of many contributors, and in particular those of Daniel Nephin, v2.0.0 has been released. You can grab it here:   https://github.com/alecthomas/gometalinter/releases/tag/v2.0.0 The biggest change since v1.x is that linting i

Re: [go-nuts] Re: GC SW times on Heroku (Beta metrics)

The wall clock is the first set of numbers, the second set is CPU. So 8P running for 8ms wall clock will result in 64ms CPU. The word "wall" was dropped to keep the line short. There will be a beta out in the proverbial next few days that could help reduce even these STW times. The original pos

Re: [go-nuts] Re: GC SW times on Heroku (Beta metrics)

Ok so it's not bad, thats good! The inital ~20 sec numbers come from the graphs that Herokus Go Metrics (Beta) provides. These must be sums in the given graph bucket which may for a 24H period add up to the high numbers I guess. I will let it run over night and see what it looks like tomorrow, th

Re: [go-nuts] [ANN] gometalinter v2.0.0 released - much faster linting

Thanks for this! If the people who care most about their code use linters, what does that say about those who write the linters? 😎 -- 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, s

Re: [go-nuts] Re: GC SW times on Heroku (Beta metrics)

Glad to have helped. The runtime team would be interested in seeing what these pauses look like in the beta. If you have the time could you send them to us after the beta comes out. On Tue, Dec 5, 2017 at 9:06 AM, Henrik Johansson wrote: > Ok so it's not bad, thats good! > > The inital ~20 sec

Re: [go-nuts] Re: GC SW times on Heroku (Beta metrics)

I would gladly help with this but afaik Heroku only makes stable versions available: https://github.com/heroku/heroku-buildpack-go/blob/master/data.json I guess I could deploy a docker container but I don't know if it changes everything and I doubt I have time before christmas at least. Maybe some

[go-nuts] Re: are interface calls to empty methods optimized away - so there is no function call overhead beyond the dereference/jump?

nice, so from a users point of view, (apart from it making no functional difference.), having interfaces of pointer types incurs no run-time overhead (well apart from the storage for the type info.). -- You received this message because you are subscribed to the Google Groups "golang-nuts" gro

Re: [go-nuts] Re: are interface calls to empty methods optimized away - so there is no function call overhead beyond the dereference/jump?

for people possibly scanning this later; when you say; "it won't store the address of the value, but will make a copy." i think this is correct/clearer; "it won't store the address of the value, but will make a copy, and store its address." On Tuesday, 5 December 2017 07:41:51 UTC, Axel Wag

[go-nuts] Re: understanding memory profile

Thanks for the pointer! I am still puzzled by the former (allocation associated with the import line). I thought it could be an init() function in this file, but that does not explain it... On Monday, December 4, 2017 at 5:47:09 PM UTC-8, Dave Cheney wrote: > > > > On Tuesday, 5 December 2017 12

Re: [go-nuts] Re: GC SW times on Heroku (Beta metrics)

Henrik, Thanks for the kind offer but there isn't much the runtime team can do with the logs since 1.9 isn't likely to be changed due to this issue. On Tue, Dec 5, 2017 at 10:43 AM, Henrik Johansson wrote: > I would gladly help with this but afaik Heroku only makes stable versions > available:

Re: [go-nuts] Re: GC SW times on Heroku (Beta metrics)

No problems! If I can get a beta running I'll revisit this thread. Cheers, On Tue, Dec 5, 2017, 19:41 Rick Hudson wrote: > Henrik, > Thanks for the kind offer but there isn't much the runtime team can do > with the logs since 1.9 isn't likely to be changed due to this issue. > > > > On Tue, Dec

[go-nuts] Re: understanding memory profile

No idea. Which 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 stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit http

[go-nuts] Bcrypt isn't comparing stored password hash properly

Hey Gophers, I have a bit of a headscratcher for you guys today, hoping someone will be able to help me track down where I've gone wrong. I have an SQLite3 database with user login info, including username, hashed password w/ bcrypt, and so on. I also have a "setup" method that is triggered on

[go-nuts] Re: Bcrypt isn't comparing stored password hash properly

In setup.go you aren't checking the errors from bcrypt.GenerateFromPassword or bcrypt.CompareHashAndPassword, do either of those return errors? The documentation for sqlite3 says "The value is a text string, stored using the database encoding (UTF-8, UTF-16BE or UTF-16LE)", could it be your dat

[go-nuts] Re: Dangers of package renaming

You may want to consider using a type alias -- similar to how golang.org/x/net/context is being transitioned to the standard library's context package. Also, Russ Cox wrote an excellent article abou

[go-nuts] Re: gomobile + go protobuf

I have the same issue , did you find a solution ? Le mercredi 8 novembre 2017 19:49:17 UTC-5, Jay Graves a écrit : > > I've been trying to use Protobufs as a data transport between go code and > native iOS and Android code. This has worked great on iOS as I can use this > to output go and objc c

[go-nuts] Re: understanding memory profile

Mystery solved. It turns out it was coming from bytes.NewBuffer which was being invoked in the method I listed. Somehow that was attributed to the import line for bytes rather than the line of invocation. On Tuesday, December 5, 2017 at 10:51:33 AM UTC-8, Dave Cheney wrote: > > No idea. Which ve

[go-nuts] Re: understanding memory profile

Can you please check if this is happening with the current version of Go and if so raise a bug, https://golang.org/issue/new. Thanks -- 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

[go-nuts] Re: Bcrypt isn't comparing stored password hash properly

The encoding hadn't occurred to me, I'll take a look. Neither return errors, as the value is properly thrown into the SQLite3 database. On Tuesday, December 5, 2017 at 12:36:26 PM UTC-8, matthe...@gmail.com wrote: > > In setup.go you aren't checking the errors from > bcrypt.GenerateFromPasswor

Re: [go-nuts] corrupt stack?

the failure rate is high enough to be motivating. :-) i now have go 1.9 working for production builds. i will report back with results as soon as i have them. - erik On Monday, December 4, 2017 at 6:16:29 PM UTC-8, Ian Lance Taylor wrote: > > On Sun, Dec 3, 2017 at 6:42 PM, > wrote: > > >

Re: [go-nuts] understanding memory profile

I’ve noticed there appear to be changes with 1.9.2 from prior versions that I have used. Still playing with it but has there been a redesign of the profiling package I didn’t notice? > On Dec 5, 2017, at 4:51 PM, Dave Cheney wrote: > > Can you please check if this is happening with the curre

Re: [go-nuts] understanding memory profile

The pprof packages are maintained elsewhere, https://github.com/google/pprof, we fork off a copy each major release. On Wed, Dec 6, 2017 at 11:45 AM, Robert Frangioso wrote: > > I’ve noticed there appear to be changes with 1.9.2 from prior versions that > I have used. Still playing with it but ha

Re: [go-nuts] understanding memory profile

Thanks Dave! > On Dec 5, 2017, at 7:57 PM, Dave Cheney wrote: > > The pprof packages are maintained elsewhere, > https://github.com/google/pprof, we fork off a copy each major > release. > > On Wed, Dec 6, 2017 at 11:45 AM, Robert Frangioso > wrote: >> >> I’ve noticed there appear to be chan

[go-nuts] Golang binary on Mac OS error “operation not permitted”

I'm trying to ship a golang binary inside a mac app. It is ideally just a http server with some basic functions on folders and files. The binary seems to work just fine when I run it from a terminal but when I try calling it from my mac app programmatically it gives an error "operation not pe