Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump github.com/golang/protobuf from 1.3.5 to 1.4.2 #9

Closed

Conversation

dependabot[bot]
Copy link

@dependabot dependabot bot commented on behalf of github Jul 22, 2020

Bumps github.com/golang/protobuf from 1.3.5 to 1.4.2.

Release notes

Sourced from github.com/golang/protobuf's releases.

v1.4.2

Notable changes:

v1.4.1

Notable changes:

v1.4.0

Overview

This release of the github.com/golang/protobuf module introduces a number of significant changes relative to the previous minor release. In particular, this module is now implemented in terms of the new google.golang.org/protobuf module, which is the next major revision of Go bindings for protocol buffers. From this point onwards, most of the development effort for Go protobufs will be dedicated to the new module, with minimal changes being made to this module.

See the release notes for the new module for specific implementation details that may affect this release.

Backwards compatibility

This release maintains backwards compatibility with previous releases of this module. Any observable changes in behavior are to fix bugs, change unspecified behavior, or to make behavior more compliant with the protobuf specification. The compatibility document provides us the freedom to make changes in these areas.

Notable changes

Wire serialization

Wire serialization is now implemented in terms of the new proto package by calling out to the relevant functionality in that package (e.g., proto.Marshal and proto.Unmarshal). There should be no observable changes in behavior other what is mentioned elsewhere in the release notes (e.g., behavior around errors or nil values).

JSON and text serialization

The JSON and text format implementations have been ported to use protobuf reflection under the hood instead of relying on Go reflection. This provides flexibility as they can operate on any concrete message type that properly implements the new proto.Message interface.

The implementations do not use the new protojson or prototext packages in order to maintain a higher degree of backwards compatibility. Our analysis unfortunately showed us that too many tests rely on their output being stable by performing byte-for-byte comparisons. Even though the compatibility promise gives us the freedom to change the output, we have chosen not to do so for pragmatic reasons. The implementations are now functionally frozen (bugs and all) and will not receive future improvements. Users are encouraged to migrate to the protojson or prototext packages instead.

Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

bogdandrutu and others added 30 commits May 14, 2020 18:31
OpenCensus go instrumentation uses 8 bytes array internally https://github.com/census-instrumentation/opencensus-go/blob/master/trace/export.go#L76, and before exporting it in OC format it's converted to a slice https://github.com/census-ecosystem/opencensus-go-exporter-ocagent/blob/master/transform_spans.go#L44. As a result root spans are exported with ParentSpanID set to 8 byte slices with all zero values. This commit make the OC->Internal trace convertor to skip those values and align it with internal representation of a root span which supposed to have ParentSpanID set to nil value instead.
* Add OTLP receiver docs

* Also move hostmetrics docs here
* Fix broken links
* Other minor cleanup

* Address feedback

* Address feedback
…1003)

* resourceprocessor: Don't panic when consumed resource has nil labels

* Address feedback
Problem: If any zipkin span attribute that is used as source for setting OC status code (like status.code, http.status_code or census.status_code) received with a type other than int64, the underlying value will be taken as an integer. For example if http.status_code sent as "200" string attribute it's got converted to status code = 2. The problem wasn't that critical until we started setting error tag based on status code dmitryax/opentelemetry-collector@75ae919 

This commit adds support of string values in status.code, http.status_code or census.status_code attributes and reject values of other types.
* Refactor common client TLS configuration.

* Formatting and such

* Add insecure options for test bed exporters

* Fix logic in opencensus exporter

* Add insecure flag to test configs

* Rename object and simplify loading of gRPC Credentials
As is, the example k8s agent fails to deploy, going into a CrashLoopBackoff:

```
{"level":"info","ts":1589972770.1904275,"caller":"builder/exporters_builder.go:95","msg":"Exporter started.","component_kind":"exporter","component_type":"otlp","component_name":"otlp"}
Error: cannot setup pipelines: cannot build pipelines: error creating processor "memory_limiter" in pipeline "traces": checkInterval must be greater than zero
2020/05/20 11:06:10 Application run finished with error: cannot setup pipelines: cannot build pipelines: error creating processor "memory_limiter" in pipeline "traces": checkInterval must be greater than zero
```

Testing:
I created a completely empty minikube and tried to apply k8s.yml from master. With this change, the agent becomes ready.

Documentation
None - caveat: as I couldn't find existing documentation for checkInterval and am just playing around right now, I don' really know if 5s is a sensible value for this.
…n provided context's cancelFn to signal end of ticker (#1017)
This was removed before but found its way back in. I'm hoping keeping it
included with // indirect but changing it to pin to sha1 will prevent it from
getting clobbered again. Added note explaining why it's pinned the way it is.
Resolves: jaegertracing/jaeger#2252
Related to open-telemetry/opentelemetry-collector#294

Just fixing the log message. The warn level was printing stacktrace what was confusing for users.
1. PICT tool input files for trace data and resulting output files from running pict from the command line. These are in `internal/goldendataset/testdata`. See: [Pairwise Independent Combinatorial Testing](https://github.com/microsoft/pict)
2. Generator for fully-populated OLTP ResourceSpans from PICT output files.

This has all the intended functionality for this PR. It has no impact on other functionality so there should be no problem in merging to master. I will follow up with other PRs to complete full "Golden Dataset" testing functionality.

**Link to tracking Issue:** #652 

**Testing:** Unit tests exist for all functionality which has been coded so far

**Documentation:** None yet. Will do so after golden dataset generation coding is complete.
This change adds application/x-protobuf support to the existing
grpc-gateway mux in the OTLP receiver.

See: https://github.com/open-telemetry/oteps/blob/master/text/0099-otlp-http.md

What currently works:
* The receiver will correctly process HTTP requests with the
  Content-Type application/x-protobuf.
* The receiver will respond with Content-Type application/x-protobuf.
* The receiver will respond with status code HTTP 200 OK on success.

What doesn't work yet:
* The receiver cannot handle gzip-encoded requests (Content-Encoding
  gzip).
* The receiver will not gzip-encode responses to requests with
  Accept-Encoding: gzip.

Updates #881
The goal is to understand who is using the OpenTelemetry Collector in
production. Other CNCF projects have taken a similar approach to
highlight adoption.
* Initial commit of host metrics virtual memory scraper for windows

* Added non-windows virtual memory scraper implementation
jchengsfx and others added 25 commits July 15, 2020 15:17
* Add details for testbed README

* add diagram for testbed pipeline

* revise diagram for testbed v1

* Added step-by-step instruction for testbed README

* Delete untitle.md and modify the content of README

* revise some expression errors of README.md

* Modified README and added a seperate Dataflow section
- Removed the draft logsproto and now using the logs Protobufs from
  official OTLP repo. The rest of the changes are forced by this.
- Added InstrumentationLibraryLogs and change the type of LogRecord.Body
  to AnyValue.
- Updated fileexporter and logexporter to use the new log data type.
* Add release documentation

* fix formatting
Bumps [go.uber.org/zap](https://github.com/uber-go/zap) from 1.13.0 to 1.15.0.
- [Release notes](https://github.com/uber-go/zap/releases)
- [Changelog](https://github.com/uber-go/zap/blob/master/CHANGELOG.md)
- [Commits](uber-go/zap@v1.13.0...v1.15.0)

Signed-off-by: dependabot[bot] <[email protected]>

Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [github.com/ory/go-acc](https://github.com/ory/go-acc) from 0.2.1 to 0.2.5.
- [Release notes](https://github.com/ory/go-acc/releases)
- [Commits](ory/go-acc@v0.2.1...v0.2.5)

Signed-off-by: dependabot[bot] <[email protected]>

Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
* Add support for queued retry in the exporter helper.

Changed only the OTLP exporter for the moment to use the new settings.

Timeout is enabled for all the exporters. Fixes #1193

There are some missing features that will be added in a followup PR:
1. Enforcing errors. For the moment added the Throttle error as a hack to keep backwards compatibility with OTLP.
2. Enable queued and retry for all exporters.
3. Fix observability metrics for the case when requests are dropped because the queue is full.

* First round of comments addressed
* Add a utility to generate metric data for testing

* Address feedback

* Address feedback
Bumps [go.opencensus.io](https://github.com/census-instrumentation/opencensus-go) from 0.22.3 to 0.22.4.
- [Release notes](https://github.com/census-instrumentation/opencensus-go/releases)
- [Commits](census-instrumentation/opencensus-go@v0.22.3...v0.22.4)

Signed-off-by: dependabot[bot] <[email protected]>

Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
This can receive logs in the [Fluent Forward
Protocol](https://github.com/fluent/fluentd/wiki/Forward-Protocol-Specification-v1) via either TCP or Unix sockets.  It supports all of the required features of the spec.

It currently does not support the optional handshake aspect of the
protocol, but will acknowledge chunk options per the spec.

All log entries received within a short time window of each other will
be put into the same ResourceLog instance before being emitted to the
next consumer in the pipline.  The Resource object is currently not
populated in any way.
Signed-off-by: Bogdan Drutu <[email protected]>
Need to wrap metric before sending out from resource processor, wrapping was lost during this change open-telemetry/opentelemetry-collector@afc4796
* Add batch size bytes metrics

Signed-off-by: Pavol Loffay <[email protected]>

* increase test coverage

Signed-off-by: Pavol Loffay <[email protected]>

* Fix metrics

Signed-off-by: Pavol Loffay <[email protected]>

* Fix test

Signed-off-by: Pavol Loffay <[email protected]>

Co-authored-by: Bogdan Drutu <[email protected]>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Jul 22, 2020
@mxiamxia mxiamxia closed this Oct 7, 2020
@dependabot @github
Copy link
Author

dependabot bot commented on behalf of github Oct 7, 2020

OK, I won't notify you again about this release, but will get in touch when a new version is available.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

@dependabot dependabot bot deleted the dependabot/go_modules/github.com/golang/protobuf-1.4.2 branch October 7, 2020 20:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.