Alfonso Acosta
Alfonso Acosta
We should also consider using something other than s3 since we may not end up using s3 in production (for cost reasons).
+1. This could get us up to a 7% speedup in the Scope probes without making any investments since we are already using your library and codecgen.
Same problem here (with Goland)
It seems to happen with clippy is enabled in the UI. Is this the case for the rest of you?
Are you using the reaper? (i.e. `--history-retention-count`). It seems like the database cannot cope with the delete queries (it's not doing them on time, causing the cancelations from Horizon) which...
One of the reasons for using [ECS AMIs](https://www.weave.works/docs/scope/latest/ami/) and [Cloud formation templates](https://www.weave.works/docs/cloud/latest/install/ecs-no-kubernetes/) is that ECS didn't provide an easy way to schedule one Scope/Weave agent per machine. [Since yesterday](https://aws.amazon.com/about-aws/whats-new/2018/06/amazon-ecs-adds-daemon-scheduling/) it...
> That's not how it works. The getaddrinfo() logic picks the IP with the longest common prefix to the local IP. In case of weave net, that has nothing whatsoever...
Related: http://kubernetes.io/docs/user-guide/ingress (k8s equivalent of `weaveworks/flux-edgebal`)
#23 and #24 would make this much simpler.
This one's tricky. In fact, we initially tried to infer the network peers from the ECS cluster members instead of the autoscaling group but there's a chicken and egg problem:...