-
The build is failing since https://github.com/crossdock/crossdock/pull/74 was merged.
This is by design, but we still need to fix it:
```
✗ [errorstchout] go→ (errorstchout=go server=go) ⇒ client re…
-
Currently we have to get a `assert` and `fails` object at the top of every test:
``` go
func Run(t crossdock.T) {
assert := crossdock.Assert(t)
fatals := crossdock.Fatals(t)
// ...
…
-
Currently, we have 3 different ReqMetas:
- `raw.ReqMeta`
- `json.ReqMeta`
- `thrift.ReqMeta`
The only difference between the 3 is that `thrift.ReqMeta` does not have a `Procedure` field, since we de…
-
We can catch panics from service handlers and return a cute error to the client instead of letting the server process crash.
-
We don't want some of the primary use-cases to cause users to reach down into the `transport` package, lets move headers up as a top-level shape instead.
-
## The Problem
@bombela, being new to YARPC, brought up a really good naming smell when he was trying to understand all the objects at play and their responsibilities -
> It took me awhile to get t…
-
We need to decide whether or not to dispatch on the triple of `(service, procedure, encoding)` or not. Currently, we route on `(service, procedure)`, and if the encoding is not correct, it will fail t…
-
Having a separate TTL concept is a bit surprising:
``` go
yarpc.ReqMeta(
Context: context.WithTimeout(time.Second),
TTL: time.Second,
...
)
```
Instead, lets start with just the context…
-
As part of https://github.com/yarpc/yarpc-go/issues/68, we'll be moving `transport.Headers` to `yarpc.Headers`. While at it, I think we should also convert headers into an opaque type. Right now,
```…
-
I've struggled with the `sink` terminology in various Crossdock behaviors - for examlpe, https://github.com/yarpc/yarpc-go/pull/147/files#diff-b84f2b2ac8e475a9c0fb53615befc070R47
@kriskowal mentioned…