mber 2, 2016 at 7:55:59 PM UTC-4, Gustavo Niemeyer wrote:
>>
>> You said the function would return whether it got cancelled or not, so I
>> assumed something like err := foo.CallAPI(ctx), which would be awkward to
>> return without actually canceling.
>>
>> Yes, if th
ssue. Which is now adding more noise and confusion (sorry. I'll shut up
now).
On Thu, Nov 3, 2016 at 12:31 AM, Gustavo Niemeyer
wrote:
>
>
> On Thu, Nov 3, 2016 at 1:27 AM, Axel Wagner > wrote:
>
>> That is actually a great point I haven't thought about and the
On Thu, Nov 3, 2016 at 1:27 AM, Axel Wagner
wrote:
> That is actually a great point I haven't thought about and the crux of the
> matter (sorry for repeating it, but I think it's worth making very
> explicit):
>
> While cancelFunc can only be called from the goroutine that created the
> context,
On Wed, Nov 2, 2016 at 9:11 PM, Ian Davis wrote:
> On Wed, Nov 2, 2016, at 10:35 PM, Gustavo Niemeyer wrote:
>
> Hello there,
>
> On Wed, Nov 2, 2016 at 11:09 AM, Ian Davis wrote:
>
>
>
> On Wed, Nov 2, 2016, at 12:56 PM, 'Axel Wagner' via golang-nuts w
Hello there,
On Wed, Nov 2, 2016 at 11:09 AM, Ian Davis wrote:
> On Wed, Nov 2, 2016, at 12:56 PM, 'Axel Wagner' via golang-nuts wrote:
>
> AIUI: A child or grandchild function is not supposed to signal that. They
> can return an error and let the parent cancel, or they can create their own
> ch
working fine on more recent
distributions.
On Nov 2, 2016 8:03 PM, "Pietro Gagliardi" wrote:
>
> On Nov 2, 2016, at 1:09 PM, Gustavo Niemeyer wrote:
>
> The problem was that git from very recent distributions linked against
> gnutls and did not support elliptic cu
Wed, Nov 2, 2016 at 9:10 AM, Gustavo Niemeyer
wrote:
> I've reverted it temporarily as I'm observing a large number of these
> messages, certainly from old git clients:
>
> tls: no cipher suite supported by both client and server
>
> Will investigate and redeploy so
I've reverted it temporarily as I'm observing a large number of these
messages, certainly from old git clients:
tls: no cipher suite supported by both client and server
Will investigate and redeploy soon.
On Wed, Nov 2, 2016 at 8:32 AM, Gustavo Niemeyer
wrote:
> Hello a
Hello all,
After complaints about the previous StartCom TLS certificate, it was moved
over to Let's Encrypt's dynamic generation of certificates using the
autocert package [1].
It's also been updated to be deployed as a snap [2], which means it's
better confined inside its system and a bit easier
It's a constant literal until it's used in a typed context.
This section explains it in detail:
https://golang.org/ref/spec#Constants
On Wed, Nov 2, 2016 at 6:09 AM, Martin Steffen
wrote:
> Hi, in the language spec, e.g. in connection with ``type assertions'' and
> ``special forms'', like
>
>
On Fri, Sep 23, 2016 at 5:02 PM, Zachary Gershman
wrote:
> Gustavo - it is not jus that YAML is well known, it is also widely used
> (as I even mentioned). It is a *standard *even though some may not want
> to consider it as such. If I can read xml in the stdlib why not yaml? And
> it is widely s
Hi Zachary,
You have already seen the thread, but for the benefit of others, Zach's
email comes from a thread raised and replied to yesterday on Twitter:
https://twitter.com/jvehent/status/778687333956587522
As I said there, the yaml spec is big, messy, and I wouldn't encourage
having the packag
Hello Gophers,
A major new release of mgo was just published with relevant enhancements
and fixes:
http://blog.labix.org/2016/08/01/mgo-r2016-08-01
Please let me know if you find any issues.
gustavo @ http://niemeyer.net
--
You received this message because you are subscribed to the Google G
Please note that the xmlpath package actually lives at:
http://gopkg.in/xmlpath.v2
On Mon, Jun 13, 2016 at 3:27 AM, Henrik Johansson
wrote:
> How does it compare to https://godoc.org/launchpad.net/xmlpath?
> I have been using it with great satisfaction but it is not complete to my
> knowledge
14 matches
Mail list logo
