Skip to content

Instantly share code, notes, and snippets.

View davecheney's full-sized avatar
🔥
more cowbell

Dave Cheney davecheney

🔥
more cowbell
View GitHub Profile
@davecheney
davecheney / stress.bash
Created August 25, 2012 12:12
stress test your packages
#!/bin/bash
go test -c
PKG=$(basename $(pwd))
set -e
while true ; do
export GOMAXPROCS=$[ 1 + $[ RANDOM % 128 ]]
./$PKG.test $@ 2>&1
done
cluster.contour.bind_errors: 0
cluster.contour.http2.header_overflow: 0
cluster.contour.http2.headers_cb_no_stream: 0
cluster.contour.http2.rx_reset: 0
cluster.contour.http2.too_many_header_frames: 0
cluster.contour.http2.trailers: 0
cluster.contour.http2.tx_reset: 0
cluster.contour.internal.upstream_rq_200: 7
cluster.contour.internal.upstream_rq_2xx: 7
cluster.contour.lb_healthy_panic: 0
[2018-06-04 04:38:13.399][1][info][main] source/server/server.cc:181] initializing epoch 0 (hot restart version=10.200.16384.127.options=capacity=16384, num_slots=8209 hash=228984379728933363 size=2654312)
[2018-06-04 04:38:13.401][1][info][main] source/server/server.cc:183] statically linked extensions:
[2018-06-04 04:38:13.401][1][info][main] source/server/server.cc:185] access_loggers: envoy.file_access_log,envoy.http_grpc_access_log
[2018-06-04 04:38:13.401][1][info][main] source/server/server.cc:188] filters.http: envoy.buffer,envoy.cors,envoy.ext_authz,envoy.fault,envoy.filters.http.rbac,envoy.grpc_http1_bridge,envoy.grpc_json_transcoder,envoy.grpc_web,envoy.gzip,envoy.health_check,envoy.http_dynamo_filter,envoy.ip_tagging,envoy.lua,envoy.rate_limit,envoy.router,envoy.squash
[2018-06-04 04:38:13.401][1][info][main] source/server/server.cc:191] filters.listener: envoy.listener.original_dst,envoy.listener.proxy_protocol,envoy.listener.tls_inspector
[2018-06-04 04:38:13.401][1][info][main] source/ser
[2018-06-04 03:56:06.564][1][info][main] source/server/server.cc:181] initializing epoch 0 (hot restart version=10.200.16384.127.options=capacity=16384, num_slots=8209 hash=228984379728933363 size=2654312)
[2018-06-04 03:56:06.564][1][info][main] source/server/server.cc:183] statically linked extensions:
[2018-06-04 03:56:06.564][1][info][main] source/server/server.cc:185] access_loggers: envoy.file_access_log,envoy.http_grpc_access_log
[2018-06-04 03:56:06.564][1][info][main] source/server/server.cc:188] filters.http: envoy.buffer,envoy.cors,envoy.ext_authz,envoy.fault,envoy.filters.http.rbac,envoy.grpc_http1_bridge,envoy.grpc_json_transcoder,envoy.grpc_web,envoy.gzip,envoy.health_check,envoy.http_dynamo_filter,envoy.ip_tagging,envoy.lua,envoy.rate_limit,envoy.router,envoy.squash
[2018-06-04 03:56:06.564][1][info][main] source/server/server.cc:191] filters.listener: envoy.listener.original_dst,envoy.listener.proxy_protocol,envoy.listener.tls_inspector
[2018-06-04 03:56:06.564][1][info][main] source/ser
package future
// A Future represents the result of some asynchronous computation.
// Future returns the result of the work as an error, or nil if the work
// was performed successfully.
// Implementers must observe these invariants
// 1. There may be multiple concurrent callers, or Future may be called many
// times in sequence, it must always return the same value.
// 2. Future blocks until the work has been performed.
type Future func() error
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
name: kuard
labels:
app: kuard
spec:
backend:
serviceName: kuard
servicePort: 80
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
name: kuard
labels:
app: kuard
spec:
backend:
serviceName: kuard
servicePort: 80
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
name: kuard
labels:
app: kuard
spec:
backend:
serviceName: kuard
servicePort: 80
[[constraint]]
name="k8s.io/apimachinery"
revision="1fd2e63a9a370677308a42f24fd40c86438afddf"
[[constraint]]
name="k8s.io/client-go"
branch="release-4.0"

Hello,

Peter Bourgon recently announced his proposal for a working group of 4-6 individuals to address the need for an official dependency management solution for Go. With the imminent release of Go 1.7 and the commencement of the next development cycle, the formation of this working group should be a high priority item.

I would like to be nominated to be part of this working group and seek your support. In doing so I wish to make clear my position that, if nominated, I would represent to the working group:

  • Simple. The solution must be simple in both implementation and use. It should do no more than the absolute minimum required to satisfy the requirements for a tool, and those requirements should be expressed as user stories for the various users of a Go dependency management tool.
  • Opinionated. The solution will recommend and support only one way to use it. There will be an absolute