Bump prost, tonic, and the generated files

[jneem]

This is the main breaking-change part of #20, so I figured it was worth separating out.

[jneem]

I'm pretty stumped by the CI failure here. I can't reproduce it locally, and clearly axum 0.6 exists...

[rnarubin]

tonic 0.8 depends on axum 0.5, while tonic 0.9 uses axum 0.6. The lock file has tonic 0.8 and axum 0.6, which are incompatible -- maybe a result of some mixups while iterating on versions?

I think a cargo update could resolve this. Though if we're making the change anyway, bumping to tonic 0.9 is probably a good idea

[jneem]

Hm, tonic 0.9 is causing a failed test ("Error, message length too large: found 10000520 bytes, the limit is: 4194304 bytes"), but also from here it seems like tonic 0.8 should use axum 0.6.

[rnarubin]

oh tonic 0.8.2 uses axum 0.5, 0.8.3 uses 0.6. maybe that was the mixup?

tonic 0.9 is causing a failed test ("Error, message length too large: found 10000520 bytes, the limit is: 4194304 bytes")

which test?

[jneem]

pubsub::publish_sink::test::message_responses_in_order. The full error is

Error: Status { code: OutOfRange, message: "Error, message length too large: found 10000520 bytes, the limit is: 4194304 bytes", metadata: MetadataMap { headers: {"content-type": "application/grpc", "grpc-encoding": "identity", "grpc-accept-encoding": "gzip"} }, source: None }

[jneem]

It's probably this.

[rnarubin]

ah yeah. others have run into this, looks like 10MB is the limit pubsub set GoogleCloudPlatform/pubsub#164

[jneem]

Ok, tonic is bumped to 0.9, and I put the pubsub size at 10MB. I made the bigtable size unlimited because I couldn't find a documented limit. (Pre-tonic 0.9 it was unlimited anyway, so this keeps the old behavior.)

Tonic-build 0.9 seems to assume edition 2021, so I also bumped the edition (which required no other changes). Finally, I bumped the MSRV to 1.63 because time insisted.

[rnarubin]

👍