When is version 3.0.0 stable? #583
Comments
|
I think it's been done very quickly, looking forward to protobuf::json |
|
Quite a lot of work is needed to make it stable (mostly polishing). And I don't work on it actively now. So it won't happen soon. Sorry. |
|
That's a shame! |
benesch
added a commit
to MaterializeInc/materialize
that referenced
this issue
Jan 18, 2022
It's time to switch from rust-protobuf to Prost. There are a few factors
in this decsion:
* The maintainer of rust-protobuf has announced that the project is
essentially unmaintained for the time being [0].
* Prost is the more popular Protobuf library across the ecosystem. In
particular, the Tonic GRPC library uses Prost, and the Tokio tracing
console uses Prost. These are both extremely important for
Materialize Platform, which we expect to be built on top of Tonic
and making heavy use of distributed tracing.
There have been been two major blockers to adopting Prost:
1. Prost lacked dynamic message support. That was miraculously fixed
last month with the release of a fantastic prost-reflect crate [1].
2. Prost embeds `protoc` in its Git repository (!). See
tokio-rs/prost#575. That is a disaster for supply chain security.
This commit patches in a Materialize-specific fork of Prost that
compiles `protoc` from source rather than using upstream's embedded
binary blobs.
[0]: stepancheg/rust-protobuf#583 (comment)
[1]: https://www.reddit.com/r/rust/comments/rsg6gx/announcing_prostreflect_a_crate_for_protobuf/
2 tasks
benesch
added a commit
to MaterializeInc/materialize
that referenced
this issue
Jan 18, 2022
It's time to switch from rust-protobuf to Prost. There are a few factors
in this decsion:
* The maintainer of rust-protobuf has announced that the project is
essentially unmaintained for the time being [0].
* Prost is the more popular Protobuf library across the ecosystem. In
particular, the Tonic GRPC library uses Prost, and the Tokio tracing
console uses Prost. These are both extremely important for
Materialize Platform, which we expect to be built on top of Tonic
and making heavy use of distributed tracing.
There have been been two major blockers to adopting Prost:
1. Prost lacked dynamic message support. That was miraculously fixed
last month with the release of a fantastic prost-reflect crate [1].
2. Prost embeds `protoc` in its Git repository (!). See
tokio-rs/prost#575. That is a disaster for supply chain security.
This commit patches in a Materialize-specific fork of Prost that
compiles `protoc` from source rather than using upstream's embedded
binary blobs.
This commit excludes one crucial piece: converting the dynamic Protobuf
decoding in the `interchange` and `testdrive` crates from rust-protobuf
to prost-reflect. I'll do that migration in a future commit to avoid
inflating the size of this PR unnecessarily.
[0]: stepancheg/rust-protobuf#583 (comment)
[1]: https://www.reddit.com/r/rust/comments/rsg6gx/announcing_prostreflect_a_crate_for_protobuf/
benesch
added a commit
to MaterializeInc/materialize
that referenced
this issue
Jan 18, 2022
It's time to switch from rust-protobuf to Prost. There are a few factors
in this decsion:
* The maintainer of rust-protobuf has announced that the project is
essentially unmaintained for the time being [0].
* Prost is the more popular Protobuf library across the ecosystem. In
particular, the Tonic GRPC library uses Prost, and the Tokio tracing
console uses Prost. These are both extremely important for
Materialize Platform, which we expect to be built on top of Tonic
and making heavy use of distributed tracing.
There have been been two major blockers to adopting Prost:
1. Prost lacked dynamic message support. That was miraculously fixed
last month with the release of a fantastic prost-reflect crate [1].
2. Prost embeds `protoc` in its Git repository (!). See
tokio-rs/prost#575. That is a disaster for supply chain security.
This commit patches in a Materialize-specific fork of Prost that
compiles `protoc` from source rather than using upstream's embedded
binary blobs.
This commit excludes one crucial piece: converting the dynamic Protobuf
decoding in the `interchange` and `testdrive` crates from rust-protobuf
to prost-reflect. I'll do that migration in a future commit to avoid
inflating the size of this PR unnecessarily.
[0]: stepancheg/rust-protobuf#583 (comment)
[1]: https://www.reddit.com/r/rust/comments/rsg6gx/announcing_prostreflect_a_crate_for_protobuf/
benesch
added a commit
to MaterializeInc/materialize
that referenced
this issue
Jan 18, 2022
It's time to switch from rust-protobuf to Prost. There are a few factors
in this decsion:
* The maintainer of rust-protobuf has announced that the project is
essentially unmaintained for the time being [0].
* Prost is the more popular Protobuf library across the ecosystem. In
particular, the Tonic GRPC library uses Prost, and the Tokio tracing
console uses Prost. These are both extremely important for
Materialize Platform, which we expect to be built on top of Tonic
and making heavy use of distributed tracing.
There have been been two major blockers to adopting Prost:
1. Prost lacked dynamic message support. That was miraculously fixed
last month with the release of a fantastic prost-reflect crate [1].
2. Prost embeds `protoc` in its Git repository (!). See
tokio-rs/prost#575. That is a disaster for supply chain security.
This commit patches in a Materialize-specific fork of Prost that
compiles `protoc` from source rather than using upstream's embedded
binary blobs.
This commit excludes one crucial piece: converting the dynamic Protobuf
decoding in the `interchange` and `testdrive` crates from rust-protobuf
to prost-reflect. I'll do that migration in a future commit to avoid
inflating the size of this PR unnecessarily.
[0]: stepancheg/rust-protobuf#583 (comment)
[1]: https://www.reddit.com/r/rust/comments/rsg6gx/announcing_prostreflect_a_crate_for_protobuf/
benesch
added a commit
to MaterializeInc/materialize
that referenced
this issue
Jan 18, 2022
It's time to switch from rust-protobuf to Prost. There are a few factors
in this decsion:
* The maintainer of rust-protobuf has announced that the project is
essentially unmaintained for the time being [0].
* Prost is the more popular Protobuf library across the ecosystem. In
particular, the Tonic GRPC library uses Prost, and the Tokio tracing
console uses Prost. These are both extremely important for
Materialize Platform, which we expect to be built on top of Tonic
and making heavy use of distributed tracing.
There have been been two major blockers to adopting Prost:
1. Prost lacked dynamic message support. That was miraculously fixed
last month with the release of a fantastic prost-reflect crate [1].
2. Prost embeds `protoc` in its Git repository (!). See
tokio-rs/prost#575. That is a disaster for supply chain security.
This commit patches in a Materialize-specific fork of Prost that
compiles `protoc` from source rather than using upstream's embedded
binary blobs.
This commit excludes one crucial piece: converting the dynamic Protobuf
decoding in the `interchange` and `testdrive` crates from rust-protobuf
to prost-reflect. I'll do that migration in a future commit to avoid
inflating the size of this PR unnecessarily.
[0]: stepancheg/rust-protobuf#583 (comment)
[1]: https://www.reddit.com/r/rust/comments/rsg6gx/announcing_prostreflect_a_crate_for_protobuf/
benesch
added a commit
to MaterializeInc/materialize
that referenced
this issue
Jan 18, 2022
It's time to switch from rust-protobuf to Prost. There are a few factors
in this decsion:
* The maintainer of rust-protobuf has announced that the project is
essentially unmaintained for the time being [0].
* Prost is the more popular Protobuf library across the ecosystem. In
particular, the Tonic GRPC library uses Prost, and the Tokio tracing
console uses Prost. These are both extremely important for
Materialize Platform, which we expect to be built on top of Tonic
and making heavy use of distributed tracing.
There have been been two major blockers to adopting Prost:
1. Prost lacked dynamic message support. That was miraculously fixed
last month with the release of a fantastic prost-reflect crate [1].
2. Prost embeds `protoc` in its Git repository (!). See
tokio-rs/prost#575. That is a disaster for supply chain security.
This commit patches in a Materialize-specific fork of Prost that
compiles `protoc` from source rather than using upstream's embedded
binary blobs.
[0]: stepancheg/rust-protobuf#583 (comment)
[1]: https://www.reddit.com/r/rust/comments/rsg6gx/announcing_prostreflect_a_crate_for_protobuf/
benesch
added a commit
to MaterializeInc/materialize
that referenced
this issue
Jan 18, 2022
It's time to switch from rust-protobuf to Prost. There are a few factors
in this decsion:
* The maintainer of rust-protobuf has announced that the project is
essentially unmaintained for the time being [0].
* Prost is the more popular Protobuf library across the ecosystem. In
particular, the Tonic GRPC library uses Prost, and the Tokio tracing
console uses Prost. These are both extremely important for
Materialize Platform, which we expect to be built on top of Tonic
and making heavy use of distributed tracing.
There have been been two major blockers to adopting Prost:
1. Prost lacked dynamic message support. That was miraculously fixed
last month with the release of a fantastic prost-reflect crate [1].
2. Prost embeds `protoc` in its Git repository (!). See
tokio-rs/prost#575. That is a disaster for supply chain security.
This commit patches in a Materialize-specific fork of Prost that
compiles `protoc` from source rather than using upstream's embedded
binary blobs.
This commit excludes one crucial piece: converting the dynamic Protobuf
decoding in the `interchange` and `testdrive` crates from rust-protobuf
to prost-reflect. I'll do that migration in a future commit to avoid
inflating the size of this PR unnecessarily.
[0]: stepancheg/rust-protobuf#583 (comment)
[1]: https://www.reddit.com/r/rust/comments/rsg6gx/announcing_prostreflect_a_crate_for_protobuf/
benesch
added a commit
to MaterializeInc/materialize
that referenced
this issue
Jan 18, 2022
It's time to switch from rust-protobuf to Prost. There are a few factors
in this decision:
* The maintainer of rust-protobuf has announced that the project is
essentially unmaintained for the time being [0].
* Prost is the more popular Protobuf library across the ecosystem. In
particular, the Tonic GRPC library uses Prost, and the Tokio tracing
console uses Prost. These are both extremely important for
Materialize Platform, which we expect to be built on top of Tonic
and making heavy use of distributed tracing.
There have been been two major blockers to adopting Prost:
1. Prost lacked dynamic message support. That was miraculously fixed
last month with the release of a fantastic prost-reflect crate [1].
2. Prost embeds `protoc` in its Git repository (!). See
tokio-rs/prost#575. That is a disaster for supply chain security.
This commit patches in a Materialize-specific fork of Prost that
compiles `protoc` from source rather than using upstream's embedded
binary blobs.
This commit excludes one crucial piece: converting the dynamic Protobuf
decoding in the `interchange` and `testdrive` crates from rust-protobuf
to prost-reflect. I'll do that migration in a future commit to avoid
inflating the size of this PR unnecessarily.
[0]: stepancheg/rust-protobuf#583 (comment)
[1]: https://www.reddit.com/r/rust/comments/rsg6gx/announcing_prostreflect_a_crate_for_protobuf/
benesch
added a commit
to MaterializeInc/materialize
that referenced
this issue
Jan 18, 2022
It's time to switch from rust-protobuf to Prost. There are a few factors
in this decision:
* The maintainer of rust-protobuf has announced that the project is
essentially unmaintained for the time being [0].
* Prost is the more popular Protobuf library across the ecosystem. In
particular, the Tonic GRPC library uses Prost, and the Tokio tracing
console uses Prost. These are both extremely important for
Materialize Platform, which we expect to be built on top of Tonic
and making heavy use of distributed tracing.
There have been been two major blockers to adopting Prost:
1. Prost lacked dynamic message support. That was miraculously fixed
last month with the release of a fantastic prost-reflect crate [1].
2. Prost embeds `protoc` in its Git repository (!). See
tokio-rs/prost#575. That is a disaster for supply chain security.
This commit patches in a Materialize-specific fork of Prost that
compiles `protoc` from source rather than using upstream's embedded
binary blobs.
This commit excludes one crucial piece: converting the dynamic Protobuf
decoding in the `interchange` and `testdrive` crates from rust-protobuf
to prost-reflect. I'll do that migration in a future commit to avoid
inflating the size of this PR unnecessarily.
[0]: stepancheg/rust-protobuf#583 (comment)
[1]: https://www.reddit.com/r/rust/comments/rsg6gx/announcing_prostreflect_a_crate_for_protobuf/
benesch
added a commit
to MaterializeInc/materialize
that referenced
this issue
Jan 18, 2022
It's time to switch from rust-protobuf to Prost. There are a few factors
in this decision:
* The maintainer of rust-protobuf has announced that the project is
essentially unmaintained for the time being [0].
* Prost is the more popular Protobuf library across the ecosystem. In
particular, the Tonic GRPC library uses Prost, and the Tokio tracing
console uses Prost. These are both extremely important for
Materialize Platform, which we expect to be built on top of Tonic
and making heavy use of distributed tracing.
There have been been two major blockers to adopting Prost:
1. Prost lacked dynamic message support. That was miraculously fixed
last month with the release of a fantastic prost-reflect crate [1].
2. Prost embeds `protoc` in its Git repository (!). See
tokio-rs/prost#575. That is a disaster for supply chain security.
This commit patches in a Materialize-specific fork of Prost that
compiles `protoc` from source rather than using upstream's embedded
binary blobs.
This commit excludes one crucial piece: converting the dynamic Protobuf
decoding in the `interchange` and `testdrive` crates from rust-protobuf
to prost-reflect. I'll do that migration in a future commit to avoid
inflating the size of this PR unnecessarily.
[0]: stepancheg/rust-protobuf#583 (comment)
[1]: https://www.reddit.com/r/rust/comments/rsg6gx/announcing_prostreflect_a_crate_for_protobuf/
benesch
added a commit
to MaterializeInc/materialize
that referenced
this issue
Jan 19, 2022
It's time to switch from rust-protobuf to Prost. There are a few factors
in this decision:
* The maintainer of rust-protobuf has announced that the project is
essentially unmaintained for the time being [0].
* Prost is the more popular Protobuf library across the ecosystem. In
particular, the Tonic GRPC library uses Prost, and the Tokio tracing
console uses Prost. These are both extremely important for
Materialize Platform, which we expect to be built on top of Tonic
and making heavy use of distributed tracing.
There have been been two major blockers to adopting Prost:
1. Prost lacked dynamic message support. That was miraculously fixed
last month with the release of a fantastic prost-reflect crate [1].
2. Prost embeds `protoc` in its Git repository (!). See
tokio-rs/prost#575. That is a disaster for supply chain security.
This commit patches in a Materialize-specific fork of Prost that
compiles `protoc` from source rather than using upstream's embedded
binary blobs.
This commit excludes one crucial piece: converting the dynamic Protobuf
decoding in the `interchange` and `testdrive` crates from rust-protobuf
to prost-reflect. I'll do that migration in a future commit to avoid
inflating the size of this PR unnecessarily.
[0]: stepancheg/rust-protobuf#583 (comment)
[1]: https://www.reddit.com/r/rust/comments/rsg6gx/announcing_prostreflect_a_crate_for_protobuf/
benesch
added a commit
to MaterializeInc/materialize
that referenced
this issue
Jan 19, 2022
It's time to switch from rust-protobuf to Prost. There are a few factors
in this decision:
* The maintainer of rust-protobuf has announced that the project is
essentially unmaintained for the time being [0].
* Prost is the more popular Protobuf library across the ecosystem. In
particular, the Tonic GRPC library uses Prost, and the Tokio tracing
console uses Prost. These are both extremely important for
Materialize Platform, which we expect to be built on top of Tonic
and making heavy use of distributed tracing.
There have been been two major blockers to adopting Prost:
1. Prost lacked dynamic message support. That was miraculously fixed
last month with the release of a fantastic prost-reflect crate [1].
2. Prost embeds `protoc` in its Git repository (!). See
tokio-rs/prost#575. That is a disaster for supply chain security.
This commit patches in a Materialize-specific fork of Prost that
compiles `protoc` from source rather than using upstream's embedded
binary blobs.
This commit excludes one crucial piece: converting the dynamic Protobuf
decoding in the `interchange` and `testdrive` crates from rust-protobuf
to prost-reflect. I'll do that migration in a future commit to avoid
inflating the size of this PR unnecessarily.
[0]: stepancheg/rust-protobuf#583 (comment)
[1]: https://www.reddit.com/r/rust/comments/rsg6gx/announcing_prostreflect_a_crate_for_protobuf/
benesch
added a commit
to MaterializeInc/materialize
that referenced
this issue
Jan 19, 2022
It's time to switch from rust-protobuf to Prost. There are a few factors
in this decision:
* The maintainer of rust-protobuf has announced that the project is
essentially unmaintained for the time being [0].
* Prost is the more popular Protobuf library across the ecosystem. In
particular, the Tonic GRPC library uses Prost, and the Tokio tracing
console uses Prost. These are both extremely important for
Materialize Platform, which we expect to be built on top of Tonic
and making heavy use of distributed tracing.
There have been been two major blockers to adopting Prost:
1. Prost lacked dynamic message support. That was miraculously fixed
last month with the release of a fantastic prost-reflect crate [1].
2. Prost embeds `protoc` in its Git repository (!). See
tokio-rs/prost#575. That is a disaster for supply chain security.
This commit patches in a Materialize-specific fork of Prost that
compiles `protoc` from source rather than using upstream's embedded
binary blobs.
This commit excludes one crucial piece: converting the dynamic Protobuf
decoding in the `interchange` and `testdrive` crates from rust-protobuf
to prost-reflect. I'll do that migration in a future commit to avoid
inflating the size of this PR unnecessarily.
[0]: stepancheg/rust-protobuf#583 (comment)
[1]: https://www.reddit.com/r/rust/comments/rsg6gx/announcing_prostreflect_a_crate_for_protobuf/
|
Tracking issue for version 3 #518 Also see https://github.com/stepancheg/rust-protobuf/blob/master/doc/past-present-future.md |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
No description provided.
The text was updated successfully, but these errors were encountered: