Eduardo Apolinario

https://github.com/unionai-oss/unionml/issues/142 tracks the work to add instructions. Closing this ticket.

As we mentioned during our sync meeting today, these are 2 separate errors: 1. This is related to https://github.com/envoyproxy/xds-relay/blob/master/integration/upstream_client_test.go#L208-L218. As @LisaLudique pointed out, a connection refused means that nothing is...

We just hit this in macOS in CI: https://github.com/envoyproxy/xds-relay/pull/87/checks?check_run_id=687179666

I spent some time clarifying how/if we could rely on [framework-level retries](https://github.com/grpc/proposal/blob/master/A6-client-retries.md) to handle this. After talking to one of the grpc maintainers [on the official gitter](https://gitter.im/grpc/grpc?at=5ef1cb9c54d7862dc4a3267d), it turns out...

When I started investigating this I toyed with this of defining our own interceptor to handle retries, but abandoned that pursuit in favor of framework-level retries. Maybe it's time to...

I can confirm grpc tries really hard to handle transient failures, it tries to reestablish the connection with a exponential back retry policy. I simulated this by cranking the GRPC...

Retrying on an already opened stream is not possible. I tried the approach of simply retrying in the case of `unavailable` errors in calls to `RecvMsg` in https://github.com/envoyproxy/xds-relay/pull/103 and all...

In the envoy slack we [mentioned](https://envoyproxy.slack.com/archives/CTULFMN91/p1600378662017300) two alternatives to fix this: - define an aggregation rules checker, similar to envoy's router check tool. - implicitly add the resource name to...

Subsumed by https://github.com/flyteorg/flytekit/pull/1150.

@wild-endeavor , original context: https://flyte-org.slack.com/archives/CREL4QVAQ/p1660922404113919. Version 6.0.0 of that package is too [recent](https://pypi.org/project/docker/#history), how about we only relax the upper bound (to something like `