André Eriksson

Interesting idea. I am not sure how easy it is to accomplish :). Your example seems to hint at exposing some kind of set operation API, where any piece of...

If I am right, this would trace the HTTP server part: ``` go func DiscoverHTTPServer(d *discover.D) { var ts http.Server // keep in scope for later teardown d.BGTrace(func() { ts...

Yeah, I see what you mean. I am not sure there is a good way to avoid that. For atomicity I think the number of traces needs to be computable...

Your proposed implementation is very similar to the one I have been working on. You can see the progress in the tracing branch here on GitHub, which implements most of...

Thanks very much @mrcampbell, those are all very valid points. Authentication keys were designed for authenticating machine users with a single application, so they do not inherit permissions for creating...

Interesting, that should work. Will have a look.

I ran into this problem as well, and it was caused by an old cached service worker. I cleaned the cache completely (under dev tools -> application in Chrome) and...

@pablopunk have you tried cleaning out the cached service worker? That cache will be port-specific, so by changing the port you're working around the problem. Curious to see if this...

Of course it should be solved! I'm just trying to help find the root cause. 🙂

Ah yes, you're right about `foo`. Consider this instead: ```go func foo() (error, error) { return nil, nil } func bar(a, b, c error) {} bar(foo(), foo()) ```