David Rauschenbach

My colleague just pointed out [EntityNamer](https://github.com/manyminds/api2go/blob/master/README.md#entitynamer), which looks like a way to work around this on the server side.

If I'm not mistaken, that use of embedding causes the both the Etcd struct and the nested Api2go struct to both have a ForeignKey field, which gives rise to ambiguity,...

@sharpner So in your example would you populate `etcd.ForeignKey=` or `etcd.Api2go.ForeignKey=`? They're two separate fields now right? Which leads to the ambiguity I was referring to.

It makes no sense to me that this chart releaser action would want to set a tag. CI+CD pipelines are DOWNSTREAM from Git actions such as the setting of a...

Somewhat related: The `mime.unqp()` function shows a call to `qp()` instead of `unqp()`

@siffiejoe you sound like you know what you're talking about. Is it your opinion that these code examples are wrong or obsolete? Or is the issue that Lua behaves differently...

I also get this error. I consider it a logic error when the data access strategy leads to non-deterministic behavior on a heavily-loaded server. This is exacerbated by LevelDB which...

I don't know enough about `say` to comment on that. What about new format specifiers that allow you to specify argument numbers, such as: ```lua say:set('assertion.equal_relTol.positive', 'Expected %s2 to equal...

Maybe the fix is just to change the README example, letting the user know that param 1 is actual, and param2 is expected.

Sections of the README where the expected/actual examples shown is mismatched with the say output: http://olivinelabs.com/busted/#defining-tests ## 1. Equals ```lua describe("some asserts", function() it("checks if they're equals", function() local expected...