Performed by deleteding all lines marked // indirect in the go.mod file
and running go mod tidy to restore the required entries.
The entries ultimately removed were probably a remnant of a prior state
of the go.mod file in this sequence.
The go.mod file was generated with the following sequence of commands:
go mod init
go mod tidy
The first try resulted in two problems.
- One problem was fixed by updating the import path of nats-server to
use semantic import v2 in transport/nats/subscriber_test.go.
- The other problem was fixed by changing the required version of
go.etcd.io/etcd to v0.0.0-20191023171146-3cf2f69b5738 which
corresponds to v3.4.3. We cannot use the v3.4.3 tag directly because
of problems within the etcd repo itself described in
https://github.com/etcd-io/etcd/issues/11154
After those two changes a second go mod tidy succeeds and produces the
go.mod file included in this commit.
Rate limiting examples might be a bit confusing when Every
method is used https://github.com/go-kit/kit/issues/698.
One could expect to see throttling expressed as
a number of requests per unit of time whereas another would see it
as an interval between requests.
* make go vet happy (renamed example function for syslog)
* adjust Zipkin OpenTracing example to use the new bridge version of zipkin-go-opentracing
* fix expected output from kit-gen due to change in gofmt handling of imports
* sd/dnssrv: fix Instancer method receivers
* sd/dnssrv: SRV record with port 0 is an error
* sd/dnssrv: test for SRV port zero issue
* .build.yml: update and fix
Sample rate is for allowing to lower traffic generated by
the statsd packets so the observations need to be dropped.
statsd server will multiple the metrics with the inverse
of sample rate to compenstate.
Fixes#778
github.com/prometheus/client_golang/prometheus recently removed some
deprecated functions including UninstrumentedHandler, and changed the
way summaries work: now, by default, they don't report any quantiles,
and you have to specify precisely which quantiles you want to see.
A name change in the upstream AWS SDK caused breakage
in cloudwatch2 metrics. This commits updates our usage
of the API to match the new upstream naming.
* Add error handler implementation to the log package
* Add error handler to http transport
* Add error handler to amqp transport
* Add error handler to awslambda transport
* Add error handler to grpc transport
* Add error handler to nats transport
* Move error handler interfaces to transport package
* Move log error handler to transport package
* Remove error logger precedence
* Improve documentation wording
* Adjust transport package documentation
* Remove ignore error
* Update examples
* Add context to the error handler signature
```golang
register := zk.NewRegistrar(client,zk.Service{
Path: "/services/hello",
Name: "abc",
Data: []byte("http://127.0.0.1:8080"),
},logger)
```
> It will be created in zk
```sh
[zk: localhost:2181(CONNECTED) 161] ls /services/hello
[_c_c83db041ac654566228b72cbd541bcb5-abc0000000006, abc]
```
**/services/hello/_c_c83db041ac654566228b72cbd541bcb5** is correct
**/services/hello/abc** is empty node
```golang
//will get 0 instance
zk.NewInstancer(client,"/services/hello/abc",logger)
//will get 2 instances, one of them is <nil>
zk.NewInstancer(client,"/services/hello",logger)
```
In my understanding, [CreateProtectedEphemeralSequential](https://github.com/go-kit/kit/blob/master/sd/zk/client.go#L241) function will be created under `/services/hello/abc`
So is this a bug? Or there's something wrong with my usage？
* .build.yml: first draft sr.ht integration
* .build.yml: working, taken from web
* .build.yml: previous version was failing, will this work?
* Revert ".build.yml: previous version was failing, will this work?"
This reverts commit 2dbc4239e1.
* .build.yml: maybe this?
* base serving, encode, decode functions
* logger
* add before encode options
* add ServerAfter functions
* add error encoder
* add finalizer
* add basic happy flow
* add ServerBefore tests
* test error flow on decoding stage
* complete the test scenarios
* refactor into more generic support by implementing lambda.Handler
* testing: ErrorEncoder to reflect behavior of encoding error as payload for AWS APIGateway event handling, as if we return error not nil to lambda it shall treated as error, and the API response would not be pretty
* add wrapper
* capitalize Lambda
* add particle an
* tidy up doc words as per suggested
* Update transport/awslambda/request_response_funcs.go
Co-Authored-By: suekto-andreas <suekto.andreas@gmail.com>
* Update transport/awslambda/request_response_funcs.go
Co-Authored-By: suekto-andreas <suekto.andreas@gmail.com>
* Update transport/awslambda/server.go
Co-Authored-By: suekto-andreas <suekto.andreas@gmail.com>
* Update transport/awslambda/request_response_funcs.go
Co-Authored-By: suekto-andreas <suekto.andreas@gmail.com>
* refactor multiline to keep them 1 per line
* remove \n from test
* defines a DefaultErrorEncoder, refactor the handling of errorEncoder during Invoke
* refactor Server into Handler
* remove wrapper
* refactor variable s into h
* simplify the return of errorEncoder
* Update transport/awslambda/handler.go
Co-Authored-By: suekto-andreas <suekto.andreas@gmail.com>
* Update transport/awslambda/handler.go
Co-Authored-By: suekto-andreas <suekto.andreas@gmail.com>
* Update transport/awslambda/handler.go
Co-Authored-By: suekto-andreas <suekto.andreas@gmail.com>
* DefaultErrorEncoder unit test
